mirror of
https://github.com/rzuasti/oott.git
synced 2026-07-08 19:21:54 +02:00
Switching between the top-level destinations went through the default CupertinoPage slide, which is meant for forward pushes. For a peer tab-switch it slid the incoming screen in over the outgoing one without animating the old screen away, leaving it visible in the background. Give the top-level routes a CustomTransitionPage crossfade; keep the device-detail route on the default slide since it is a genuine drill-in. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
OOTT ToDo list
- Add support for push notifications to the app (iOS and Android)
- Modify the release script to check that gh is logged in and that frontend tests are run before releasing
Release plan for 0.2.0
- Test Android UI on emulator
- Release 0.1.0
- Fix bugs and release 0.1.1
- Install in test server (docker) following documented process
- Install test app on iPhone
- Test in-house for 1 week
- Implement push notifications
- Release 0.2.0
- Install in test server and test app on iPhone
- Test in-house for 3 days
- Release 0.2.1 (or as many versions as needed)
- Publish website
- Post on reddit
Backend
- In notifications, when its a new device(s) found notification, remove the status block (new devices are never registered)
- In notifications, when the vendor is empty put (unknown)
- Implement the pushover API call directly to support HTML content and review notification text to use it
Frontend
- The app has the default Flutter icon in iOS, use OOTT's icon
- Ask for network access when the app launches, now it asks when you try to test the connection for the first time and it always fails once
- On iOS when the user navigates between screens the previous screen remains visible on the backgroun while the other one animates in, it looks bad
- In narrow devices, the "Notifications" title in the home screen is to close to the filter combobox and does not scroll with the page (it should)
- When the user goes to the / URI in a production server redirect him to /web
- Add a link to the API docs (/api/docs) in the navigation (new window - only visible in wide)
Improve engine
Passive (low noise, no probing):
- Passive packet capture — observe any broadcast/multicast traffic; a device that never responds to ARP still generates traffic
Active (you probe the network):
- NDP (Neighbor Discovery Protocol) — IPv6 equivalent of ARP; important if the network uses IPv6