Stride
K12 Learning Coach Community: Website and Mobile Apps
Stride's Learning Coach Community for K12 families: native iOS and Android apps and a full website from one codebase, where learning coaches message, meet and share resources.
Challenge
Learning coaches needed one place to connect with each other: messaging, events, groups and shared resources, on whatever device they had, with UNA CMS as the community backend.
What I built
- Architected the app from scratch: one React Native codebase that ships native iOS and Android apps plus a full desktop web experience.
- Real-time messaging with attachments and private document previews, events, groups, a resource library, push notifications and content moderation.
- Coach matching by shared interests and ZIP-code proximity.
- Custom UNA CMS modules for a redesigned email and notification system, with versioned schema migrations.
- Led the desktop web expansion with React Native for Web: wrote the architecture decision record, scoped the work into 16 tickets, and built the desktop shell without changing the native apps.
How it works
One codebase, three platforms
The app is React Native with Expo, built for iOS and Android with EAS. For desktop web I compared React Native for Web, a separate React app and a shared-core monorepo in an architecture decision record, and chose React Native for Web: the browser runs the same business logic, with web-only files where the desktop needs its own layout, so the native apps stay untouched.
A Laravel layer between the app and the CMS
UNA CMS runs the community, but its API is slow and shaped for the CMS, not the app. A Laravel service sits in between as the app's backend: it normalizes CMS data, keeps app-specific tables in PostgreSQL on AWS, issues tokens with Sanctum, and delivers real-time messages over WebSockets with Laravel Reverb.
Making it fast
The slowest screens made dozens of CMS calls per page, an N+1 pattern. I moved those reads to batched queries against a read replica and ran independent requests concurrently, each behind a kill switch that falls back to the CMS automatically, and checked that the responses matched. Event search went from about 25 seconds to 3. When one direct path measured 3 times slower, I reverted it.
Matching coaches
Coaches are ranked by shared interests and by distance between ZIP codes, using the US Census ZIP code areas (about 33,000 of them). Onboarding saves optimistically and prefetches matches in the background, so it never waits on the network, and new connections arrive as push notifications.
Private by design
Word, Excel and PowerPoint previews are converted to PDF with LibreOffice on our own servers, because hosted viewers from Microsoft or Google would have to fetch parents' files themselves. Reported conversations and their attachments are preserved as evidence even after deletion, with a one-year retention sweep.
Guardrails from day one
Husky, commitlint, Jest and SonarQube in Bitbucket Pipelines from the first weeks, API docs for 212 routes with a build check that fails on any undocumented route, and an uptime monitor that checks 5 upstream services every 5 minutes and alerts Slack only when something changes.
Results
- Cut response times 70 to 88% on the slowest API endpoints; event search went from 25 seconds to 3, each change behind a kill switch with automatic fallback.
- Automated health monitoring of 5 third-party integrations with Slack alerting.
- Automated tests and SonarQube quality gates in CI/CD.