Client web UI and PWA
The client UI is served at /. It is browser-first, works on desktop and mobile browsers, and can also be installed as a PWA where the browser supports it.
- Chore lists, completion flow, proof photos, approvals, and takeover requests.
- Group, type, and optional sub-type labels on chore cards so the selected template structure is visible in day-to-day use.
- End-user language, theme, notification, and device settings.
- Foreground live sync while open and optional background Web Push when VAPID keys are configured.
Admin web UI
The admin UI is served at /admin and uses session storage so admin access is scoped to the current browser session.
- Household settings, member management, grouped templates, types, sub-types, and translation management.
- A compact Templates editor with grouped browsing, search, and language tabs for maintaining translated group, type, and description text without excessive vertical scrolling.
- Auth, SMTP, backup-readiness, notification recovery, runtime logs, and system status.
Native Android app
The Android app remains supported while the browser/PWA client matures. It talks directly to the API server and supports mobile-first chore usage, offline queueing, proof photos, and the widget foundation.
Android push behavior
Android push is optional and degrades cleanly.
- If the Android app is built without Firebase values, it still runs and registers as a generic notification device.
- If the app is built with Firebase app settings, it initializes Firebase at runtime and registers an FCM token when available.
- If the server is also configured with
TASKBANDIT_FCM_ENABLED=trueand a Firebase Admin service account, queued household notifications can be delivered as real Android push notifications.
Notification priorities
TaskBandit treats mobile/browser push as the primary notification path for household activity. SMTP-backed email is intended for account recovery, admin-style messages such as invites, and fallback delivery when no push-ready device is available.