mirror of
https://github.com/rzuasti/oott.git
synced 2026-07-08 19:21:54 +02:00
rzuastiandClaude Opus 4.8
0a899b7890
On phone-width layouts (< Breakpoints.medium) the notification and device lists now request fewer items per page so the list and its pagination bar fit on screen together on common current phones. Notifications use 4 items and devices 6 on phones; wider layouts keep 5 and 10 respectively. The initial fetch is deferred to didChangeDependencies so the page size can read the screen width from MediaQuery. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
OOTT ToDo list
- Add support for push notifications to the app (iOS and Android)
- README.md - Add section about securing access (reverse proxy, never expose to the internet, etc.)
- README.md - Simplify storage section (remove the calculations - just leave the results)
Release plan for 0.2.0
- Test Android UI on emulator
- Release 0.1.0
- 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
- Implement the pushover API call directly to support HTML content and review notification text to use it
Frontend
- Mobile - Implement pull to refresh on the notifications and devices list
- Mobile - reduce lists length (# of items) so they fit on a phone in one screen (use iPhone latest gen and Google phone latest gen)
- Mobile - In the devices list the filters and sort buttons overlap (dont fit in the screen)
- When changing pages (either list) the items should change to placeholders while loading
- The notifications list should not refresh coldly every time. It should add/remove notifications with an animation as if a stack
- Make gruvbox the default theme
- Can we add front-end tests?
- Break down oott_api.dart in modules
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