mirror of
https://github.com/rzuasti/oott.git
synced 2026-07-08 19:21:54 +02:00
rzuastiandClaude Opus 4.8
67b94b89a1
Settings screen now splits responsibilities: - Backend URL + API key move into a Test/Save popup dialog (backend_config_dialog.dart), reachable via a "Re-configure" action. Per M3 the Test button is left-aligned (neutral) with Cancel/Save grouped trailing. On first run the dialog auto-opens non-dismissible. - The screen shows the connection read-only (URL plain, key masked with reveal) in a "Backend connection" card, and groups Theme + Push into an "App settings" card. Theme and push apply immediately, no Save button. - Align all card titles to titleLarge across home/status/settings. Adds a test seam (dioBuilderForTesting) so reconfigure keeps the mock Dio in widget tests instead of issuing real requests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
OOTT ToDo list
- Add support for push notifications to the app (iOS and Android)
- Remove push notifications plan
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
- Implement the pushover API call directly to support HTML content and review notification text to use it
- Check for potential dependency upgrades
Frontend
- In the status screen, the "listening for" property of passive scanners should change to days and months (now its always minutes)
- Check for potential dependency upgrades
- In the frontend, in the settings screen, move the backend configuration to a popup dialog that asks for the URL and API key and allows the user to test and save it. In the main screen it should present both items as read only and allow the user to change the theme and push notifications and both should trigger the change immediately (ie. without a save button). The dialog for the backend config should be accesible via a "Re-configure" link or button (do what aligns best with M3). The first time the user uses the UI (or when the backend is not configured at all, it should navigate to the settings screen with the dialog open, and upon Saving the backend config it should refresh the settings page)
- The permissions dialog for push notifications on android says "Allow frontend to send you notifications"
Push relay
- Add NPM to the devShell to be able to run tests
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