BUILD STORY
In Development
Tamo
Fitness & Meal Tracker
A mobile app for workouts, meals, progress tracking, and personal health routines.
- Type
- Mobile App
- Category
- Apps & Products
THE NEED
A health tracker should fit the routine—not make the routine harder.
I wanted one place to shape the workouts, meals, and progress routines I actually use, without carrying extra features or another recurring subscription for a workflow I wanted to own and adapt. Tamo began as a personal, local-first alternative built around that narrower need.
THE PRODUCT DECISION
Build the dependable daily foundation before adding broader coaching features.
The product is being developed as an iPhone-first mobile app with local data ownership at its core. Instead of trying to ship every health feature at once, the build is progressing through focused vertical slices—starting with a durable app shell and workout system before deeper nutrition and progress workflows.
DESIGNING THE EXPERIENCE
Keep repeated actions close, recoverable, and usable offline.
The experience uses a stable mobile shell, restrained feedback, accessible controls, and durable local records. Workout sessions, routines, and exercise selections are modeled separately so an interrupted session can recover cleanly and completed history will not be rewritten when a routine changes later.
PRODUCT IDENTITY
Tamo's current product identity
The available portfolio visual shows Tamo's established app identity while the working product continues through its workout-system build.
CURRENT BUILD
What exists today—and what is still being built.
Implemented
- Accessible Expo app shell with navigation, light and dark themes, haptics, and local profile foundations
- SQLite workout domain with recoverable sessions, immutable history snapshots, and routine persistence
- Exercise library with search, filters, favorites, custom exercises, and contextual add or replace flows
- Active workout composer with routines, exercise ordering, persisted duration, and rest defaults
In Progress
- Active-workout set logging and the complete finish or partial-workout flow
- Physical-device validation of the workout card, rest selector, completion sound, and accessibility behavior
Planned
- Meal and hydration logging beyond the current placeholder actions
- Weight and progress tracking beyond the current placeholder actions
- Curated programs and workout-progress integration
WHAT I'M LEARNING
The product gets clearer when the underlying rules do.
- Durable local records and recoverable drafts need to come before richer workout controls.
- A stable shared shell makes it possible to add feature depth in focused vertical slices without repeatedly restructuring navigation.
- Rest behavior belongs in the session model, so interface refinements do not have to rewrite exercise data.
SYSTEM DETAILS
Project Details
- Category
- Apps & Products
- Type
- Mobile App
- Status
- In Development
- Platform
- iPhone-first mobile app
Stack
- React Native
- Expo SDK 54
- TypeScript
- Expo Router
Data & Architecture
- SQLite local storage
- Feature-first modules
- Repository and service boundaries
- Stable local identifiers
Current Focus
- Workout sessions
- Exercise library
- Routines
- Rest defaults and recovery
WHAT'S NEXT
Meaningful milestones, kept deliberately focused.
- Complete set logging and workout finish, partial, and history-review flows
- Validate the active workout experience on a physical iPhone
- Advance nutrition and progress beyond placeholders after the workout loop is dependable
- Build curated programs and connect workout history to progress views
The goal is not to recreate every health app. It is to build the focused system I want to keep using.