Is ForeKids in the app stores?

No. It is in beta on Android, installed directly by the families on our team, with a web app alongside it. The project has iOS targets, but the iOS build is not done.

Why one codebase for the phone and the web?

The screens live in one Razor component library. A .NET MAUI Blazor Hybrid app hosts it on the phone and a Blazor WebAssembly app hosts it in the browser. One team builds one interface, and a fix lands in both places.

How does offline sync avoid duplicate scores?

Every write goes into a queue on the phone with its own idempotency key. When the connection comes back the queue replays in order, and the server recognizes a key it has already processed and ignores the repeat.

Is there AI in the app?

No, and that was a decision, not an omission. The app is for children. AI was used to plan, write and review the code, with every change reviewed in a separate session before it merged.

How do children get accounts?

Young players do not sign themselves up. A coach or a parent creates the account. A linked parent can read their child's chat channels, and the app tells the player that on screen.

Youth Sports / Mobile

ForeKids: A Junior Golf Team Platform

A mobile and web app for running a junior golf team. Coaches assign drills and track progress, players log rounds and practice, and parents follow along. One codebase, and it keeps working when the course has no signal.

Client: In-house buildTimeline: Started April 2026, in beta

.NET 10.NET MAUIBlazor HybridBlazor WebAssemblyASP.NET CoreEF CoreSQLiteAzureAndroidOffline Sync

The Challenge

This one started at home. We coach junior golf, and a team of players aged 8 to 17 needs a few things no general sports app does well: scores logged hole by hole, practice a coach can assign and then see, a schedule, and a way for parents to follow their own child.

Three constraints shaped the build. A golf course is not a place you can count on a signal, so anything a player records has to survive being offline. The users are children, so the design that works for a high schooler does not work for a second grader. And it had to be built on evenings and weekends, on a hosting budget of $50 a month.

It is a fun project with real use, and it is where we prove out mobile patterns before they reach client work.

Our Approach

We wrote the interface once. A single Razor component library feeds two apps: a .NET MAUI Blazor Hybrid app for the phone, Android first, and a Blazor WebAssembly app for the browser. A fix to a screen lands in both.

The API is ASP.NET Core with EF Core on Azure SQL. On the phone, a local SQLite store backs a read-through cache and a first-in, first-out queue of writes. The screen updates right away, the queue drains when the connection returns, and an idempotency key on each write lets the server ignore a replay.

There is no AI inside the app, and that is deliberate. It is an app for kids. AI did its work on our side of the screen: every unit was planned, challenged, built, and then reviewed in a separate session that had not seen the code being written. Findings from those reviews became permanent convention tests, so the same mistake cannot come back unnoticed.

The Solution

Three ForeKids phone screens: the team home with its leaderboard, the practice tab with an assigned drill, and the round scorecard.

Rounds and the Quick Scorer

Hole-by-hole round logging with an OUT, IN and TOT scorecard and a team leaderboard. The Quick Scorer keeps a live draft a player can leave and come back to. Courses can be searched and imported, and par fills in from the course.

Practice and Drills

A core catalog of 249 drills. The coach assigns drills, players log sessions against them, and an effort scorecard shows where the practice time went by category.

Badges, Streaks and Rewards

Badges are awarded automatically, practice streaks are tracked, and points add up toward a reward shop the coach controls. It gives a 9-year-old a reason to open the app again tomorrow.

Works Without a Signal

Rounds, practice and chat messages are queued on the phone and synced later. Each queued write carries an idempotency key the server honors, so a retry cannot create a duplicate. We tested it on real phones in airplane mode.

Three Looks by Age

The interface is skinned from the player's birthdate: Rookie, Player and Tour, with a separate coach view. A young player and a high schooler get the same data in a design built for each of them.

Team, Schedule and Chat

Coaches create the team, manage the roster and set up accounts for the kids. The schedule takes RSVPs. Team chat lets a linked parent read their child's channels, and the app says so on screen.

Results

249

Drills in the core catalog

500+

Automated tests

Age-based skins, plus a coach view

Junior rule summaries, searchable offline

Component library behind the phone and web apps

$50

Monthly hosting budget

ForeKids is in beta with the families on our own team. It installs on Android directly, not from an app store, and the web app covers everyone else.

Offline sync has been confirmed on real devices, including rounds and practice logged in airplane mode and synced afterward without duplicates.

Still ahead: push notifications for chat, an iOS build, and a parent dashboard. A public release would need a formal children's privacy review first, and we have not done that yet.

“A mobile app gets judged where the signal is worst and the user is least patient. ForeKids was built for a 9-year-old on the back nine with no bars, and that is a harder test than most business apps ever get.”

Frequently Asked Questions

Need a Mobile App That Works Without a Signal?

We build mobile and web apps from one codebase, with offline sync that holds up in the field. Tell us where your users lose their connection.

Explore Custom Development