Multi-platform Flutter with Firebase Auth, Firestore, Storage, Cloud Functions, rich HTML.
OurTeachers needed one Flutter codebase targeting Android, iOS, and web so a small team could ship rich lessons, attachments, push notifications, and instructor dashboards without maintaining three separate UI stacks.
Multi-target Flutter project with Firebase Auth, Firestore for structured lesson metadata, Storage for media, Cloud Functions for server-side automation, image_picker for uploads, and flutter_html for article bodies with cached images.
Firebase Auth, Cloud Functions triggers, and Storage rules had to behave consistently on Flutter web and mobile; long HTML lesson bodies needed flutter_html (and selective WebView) without desktop-only hacks that broke accessibility.
Platform folders, responsive layouts, and feature flags for web-only capabilities.
Firebase Auth with instructor vs student claims mirrored in Firestore rules.
Rich text/HTML bodies, attachments in Storage, versioning for updates.
FCM for mobile; web push strategy as applicable; Cloud Functions for server triggers.
image_picker + compression helpers before Storage writes.
Play Store, App Store, and Flutter web share widgets and theming — instructors onboard once, content propagates everywhere, and hotfixes ship as a single pipeline instead of three divergent release trains.
Play Store, App Store, and Flutter web share widgets and theming — instructors onboard once, content propagates everywhere, and hotfixes ship as a single pipeline instead of three divergent release trains.
Auth, database, storage, and functions from one control plane suited the team size.
flutter_html kept most lesson rendering accessible compared to full-page WebViews.
Let schools without managed devices access lessons from browsers using the same code.
Firestore security rules became the single source of truth for role boundaries across targets.
Sonic DeFi indexing
We take on a small number of projects at a time. If the problem is hard, we're interested.