/01
The Problem
Most wellness apps either handle scheduling or guided sessions well, but rarely both in one coherent, personalized experience.
/02
What I Did
I designed and implemented the app's local data model in CoreData — defining entities and relationships for sessions, routines, and meal plans — to independently build an end-to-end iOS wellness app in Swift/SwiftUI. I then built the logic to query and randomize that stored data into an auto-generated daily exercise calendar and a personalized meal-planning module for breakfast, lunch, and dinner.
/03
What I Found
Building a complete product solo taught me to think about a project the way a user experiences it end-to-end, not just as isolated technical pieces — a mindset I now bring into data projects too.
/04
Trade-offs & What's Next
Working solo on a bachelor's thesis timeline meant scoping trade-offs constantly — I chose CoreData over a backend/sync layer to keep the persistence model simple and ship a complete, working product rather than a half-built one with cloud sync. With more time, adding CloudKit sync and a proper watchOS companion would be the next additions.
/Tech stack
- Swift
- SwiftUI
- CoreData (local data modeling)