Team platform (Scrum) · 2025–2026
RunSafe
Platform for an external client where runners share how safe a place feels. First a 12-week React Native MVP, then rebuilt from scratch into an app, a website with a CMS and a Spring Boot API. Website and API run live, with Docker and CI/CD.
The problem
Runners don't feel equally safe everywhere, but that knowledge stays in their heads. The client wanted a map where runners share how safe a place feels, without anyone being trackable or identifiable.
- Role
- Member of a four-person Scrum team, with the most commits in all three repos
- Stack
- React Native · Expo · Angular · Spring Boot · MongoDB · Docker
Decisions
1
An honest audit first, then a rebuild
In season two, version 1 couldn't carry the product any more: the backend was offline, most tests were red and a secret key sat in the source code. We rebuilt everything from scratch, with the backend and privacy as the foundation.
2
Contract first, one API for everything
A modular Spring Boot monolith on Java 25 with MongoDB as a replica set, so transactions work. Each module gets an OpenAPI contract first, so app and website build in parallel. JWT with refresh tokens, and Swagger only outside production.
3
Shipping without the stress
I set up the production rollout: Docker Compose, a Caddy proxy with a staging setup you can switch over and roll back safely, and CI/CD that builds, tests and deploys on every merge to main.
Under the hood
Three codebases, one API, one command to ship.
Expo · React Native
Runner app
- Map with safety pins and a heatmap
- Organise and join group runs
- iOS, Android and web from one codebase
Angular
Website + CMS
- Public site, live
- Editor with draft and publish
- Roles for editor and admin
Caddy
TLS and routing, with a staging setup you can switch over safely
Java 25 · modular monolith
Spring Boot API
- Auth · JWT + refresh
- Profiles
- Pins · GeoJSON
- Group runs
- Friends + notifications
- CMS
MongoDB
Replica set for transactions; validators and indexes through a dedicated migration job
Shipping
- 1Merge to main
- 2GitHub Actions tests and builds a Docker image
- 3Docker Compose refreshes the container on the server
Two seasons
2025
MVP in 12 weeks
React Native app with a map, pins and safety zones. Two-week sprints, together with the client.
Sep 2026
Audit of version 1
Backend offline, tests red, a secret key in the code. Decision: rebuild from scratch.
Oct 2026
Foundation and shipping
Data model, API contracts and the pipeline to production. Website and API go live.
Nov 2026
The app connects
Placing and editing pins through the new architecture, and the app moves to Expo SDK 58.
Outcome
From a 12-week MVP to a platform with three codebases: website and API run live on our own server, and the app is now being connected to the API. Learned: judging a legacy honestly, agreeing contracts before building, and designing privacy in rather than bolting it on.