Client
Script (script.nl)
Day
mate.
A planning app for people who need structure in their day. This app was originally built by another company and was later taken over by Script. During my six-month internship I rebuilt it from scratch in Flutter, one codebase for iOS and Android. Five years later still live and used daily.
01 · Activity timer
02 · Day view
03 · Activity detailThe brief
Script (script.nl) is a Dutch care organisation in Groningen that runs ICT learning and work programmes for children and adults with autism or giftedness. About 150 active clients, spread across day activities, custom and reintegration. Their motto: "no adapted work, just real work." Clients learn to program, take on projects, and work toward jobs in regular IT.
Daymate was made for that same audience: people who like to organise their day in fixed blocks. Morning routine, work, breaks, end of day, with notifications at the times they choose themselves. Predictable structure is not an extra here, it is the core of the product.
Script took Daymate over from another company. The idea was right, but the execution was not yet: an MVP that did not work as intended and missed what it was supposed to do on important parts. My internship assignment had three steps: investigate whether the existing codebase was repairable, and if not, choose an alternative and rebuild both the front and back end.
Approach.
Method01
Diagnose
In the first weeks I got the existing app working on both platforms so I could see where the problem actually sat. The codebase was split into a separate version for iOS and a separate version for Android, which had drifted apart in several places. As a result every fix effectively had to be made twice, and it turned out hard to get the app structurally working.
02
Decide
Based on the diagnosis I concluded that only a rebuild would work. For the tech I chose Flutter: one codebase for both platforms, performance close to native, and its own way of rendering instead of translating to separate iOS and Android components like other cross-platform frameworks do. At the time that made it a promising choice, and in hindsight it turned out to be the right one.
03
Build
For the backend and login I used Laravel and MySQL. Notifications go through Firebase, and they are crucial — without notifications the app does not work. Mixpanel tracked what was used and what was not, so decisions could lean on data. I wrote the code and made the architectural choices; the lead developer reviewed where that helped, and the project manager guarded scope with daily standups.
04
Live
Before Daymate landed in the stores, I first tested it internally with clients who were interested. After that it went public, and was in both the App Store and the Play Store after six months. Five years later it is still used daily in the care settings it was meant for. By now another engineer at Script has taken over development, fixing bugs and adding new improvements.
04 · Activity edit flow
05 · Settings
06 · Information menu"Great app, so nice!"— Play Store review
5y
Live and used daily
Daymate went live in 2021 and has been used daily ever since in the care settings it was made for. Another engineer at Script now works on it further.
~130
Monthly active users
A small, dedicated group of people in a specific care context. Not a mass-market product, but an app that does what it needs to do for the people who need it.
1
Codebase for two platforms
Two separate native versions replaced by one Flutter codebase. That meant a colleague could pick the project back up five years later without first having to learn two separate codebases.
Stack.
Built withFlutterDartLaravelMySQLFirebaseMixpaneliOSAndroid