Equine Integration
A Flutter prototype for a company that coaches horse training with data: clearer training insights, and reasons to open the app every day. A student team project for a real client.
- Feature branchwhere the work happens
- Merge requestthe only way into dev
- devprotected
- Merge requestthe only way into main
- mainprotected
The problem
The client’s app showed a lot of training data that riders found hard to read. We were asked to make it clearer, and to give people reasons to open the app every day.
My part
- Git. My teammates were media students who had never worked with Git, so that’s where I put my focus. I set up the GitLab repository and the branching strategy: protected main and dev, and changes only through merge requests. I explained it to the team with a diagram, and did most of the merging: 25 of the 32 merges.
- The horse overview. I designed it from sketch to Figma, then built it in Flutter from reusable widgets, with a shared horse model the rest of the team used.
- Scrum master. I set up the Jira board with a teammate, prepared the client meetings and wrote the user-test plan.
What went wrong
We first received the wrong designs, and the real data arrived in week 10 of 11. In the user test, the tester didn’t see the value of my overview page, so I proposed replacing its menu button with a teammate’s ranking page. Sometimes you drop your own feature.
Status
Finished: the prototype was delivered to the client. The code belongs to the client, so there’s nothing to link to.