Original post. AI is starting to make native frontend development feasible again. Here’s a sneak peek at my upcoming scoreboard app: phone and watch apps plus a web-based courtside dashboard view you can use right next to the action.

The first version targets tennis and padel, with fully native mobile apps for Android and iOS, and watch apps for Wear OS and watchOS.

The funny thing?

The iOS versions didn’t exist last week.

On Friday, I kicked off a refactor – turning my Android-only codebase into Kotlin Multiplatform. That let me encapsulate business logic like game rules and server communication into a shared core, while still building truly native UIs on each platform.

On Saturday, I built the first native iOS views.

On Sunday, I added the watchOS version.

Yesterday, I added the shared session handling.

There’s still a lot of polishing to do and plenty of features missing – but the whole thing already works end-to-end, and all four devices successfully update the same session, which feels pretty amazing.

In the video, you can see the real time dashboard in the background and different device emulators dragged on top of that, taking turns updating the score.

In this project, the original reason for building native UIs was to guarantee performance in the watch environment. But the approach has worked so well that it’s starting to look like a genuinely viable alternative to React Native, Flutter, and the like.

—

All in all, it’s starting to feel like this vibe-coded hobby project might actually ship one day.

The original idea was to track not only who won the point, but also who was the last player to touch the ball. That opens up some intriguing possibilities for deeper statistics and new ways to analyze the game.

If you’re interested in testing the beta version soon, let me know – there’s a link in the comments. I’d love to hear which sports I should support next, which custom rules you’d need, and what kinds of stats would be most valuable to you.