← All case studies Case study · K-12 Education

One login for everything a learning coach needs.

Learning coaches used to sign in to a different system for community, grades, assignments, schedules, and live classes. We took the app from concept and discovery to beta and launch, and it now brings seven systems into one app on iOS, Android, and the web.

Client
National online K-12 education provider
Our role
Tech lead: architecture, performance, deployments, QA, and discovery
Team
19 people: 8 developers, 6 designers, 2 product managers, 2 QA engineers, 1 DevOps
Timeline
July 2025 to launch in fall 2026, from concept to the app stores
Platforms
iOS, Android, and web from one codebase
Stack
Expo, React Native, Laravel, Firebase
7 → 1sign-ins a coach no longer needs: identity, community, grades, live classes, schools, feedback, push
19people across product, design, engineering, QA, and DevOps
2,000beta users across 4 schools before full release
−62%timeline payload size, with no added server time

Performance figures were measured on a staging server across 15 scenarios, not production.

The challenge

The information was all there, in too many places.

A learning coach supports a student’s school day from home. To do that well, they need to see how the student is doing, what is due, what is live today, and where to get help from other coaches. Each of those lived in a separate system with its own login. The goal was simple to say and hard to build: one app, one sign-in, one place to look.

Discovery

How we started

Start from nothing, then find the real problem.

The first commit in the repository is a blank project from July 2025. Discovery started before that and kept running through beta.

Listen

Coach interviews and workshops.

Sessions with 10 to 25 coaches showed which questions they asked every day and what they did to answer them.

Audit

A system-by-system audit.

We mapped where each answer lived, and what each source could and could not expose.

Measure

Survey and usage data.

Existing data helped rank what to build first, so the first release covered what coaches needed most.

What we found

The simplest finding mattered most.

Coaches were juggling too many logins to do one job. Everything else followed from that.

Interviews and workshops showed which questions coaches asked every day. The system audit showed where each answer lived and what each source could expose. Survey and usage data helped rank what to build first.

What surprised us was that the data was harder to reach than the screens were to design. Some sources only answer from inside the client’s network. The sign-in provider’s school claim can be blank. Grades and assignments sit behind a data service that fronts older systems. Each of those became a rule in the middleware, so the app never has to know.

What discovery produced

Four things the rest of the project built on.

01

A system map.

Every source and how data flows between them, so everyone worked from the same picture.

02

A prioritized scope.

What made the first release and what waited. The web version and the advanced schedule (search, week view, live classes) came in later releases.

03

An architecture decision.

Put one middleware in front of every source, with the boundaries of the existing community platform written down.

04

A design brief.

A shared starting point for the six designers, grounded in what coaches told us.

Need experienced people on a software initiative?

Tell us what you are trying to move forward, what roles you need, and where your team is stretched. We will help you understand the right team shape and whether Tilted Windmill is a fit.

Talk Through Your Team Needs →

Client details are withheld. Figures are from the 2.0.3 release notes and an April 2026 performance measurement report.