Interfaces
Interface projects
Screens, flows, and prototypes — from Figma to code, with links to explore each project live.
Projects
- Year
- 2026
- Made with AI
- Design system — FigmaApp — Flutter and SupabaseCode — Claude Code
Maestro
A training app that connects coach and student. Either one can start the link: each has a code, so the coach can add the student and the student can add the coach. The coach builds the routine and follows progress, the student logs every set on their phone. My first native app, from the design system in Figma to the Flutter code.
- Role
- End-to-end, solo and authorial creation: product, design system and the orchestration of the AI agents that wrote the code.
- Goal
- Build a better training app than the ones I used, connecting coach and student, and learn Flutter along the way: it is my first native app.
- What I did
- I created the AI that helps the coach build workouts. It reads the student’s history and the health condition they share, only suggests load when there is training history, and refuses diagnoses, medication and diets. Every draft goes through the coach’s review before it reaches the student.
- I also created an AI for people who train without a coach. The student chats with it and it builds the workout, with the same health guardrails; anyone who already has a plan from their trainer can import the PDF or paste the text. Nothing saves on its own: the workout only goes in when the student accepts the draft.
- I built an integrated design system: the code is the source, and Figma is one of its layers. It has more than 130 components, from base pieces to charts and full screen compositions, on top of 127 tokens. The documentation is generated from the code, a catalog renders each component on mobile and on wide web with the same code, and a test checks that Figma uses the same token names.
- I’m not a developer. The code was written by AI agents I created and orchestrated, with guardrails for security, privacy law and code quality. I launched the app and keep adjusting it from real use: in October 2026, 3 coaches and 17 students use Maestro.
Launch video
On the phone
Student and coach · 5 screens
On desktop
Coach dashboard · 3 screens
Process
From the design system to the app
user interface (ui)
Interface projects
Screens, flows, and prototypes — from Figma to code, with links to explore each project live.
Maestro
A training app that connects coach and student. Either one can start the link: each has a code, so the coach can add the student and the student can add the coach. The coach builds the routine and follows progress, the student logs every set on their phone. My first native app, from the design system in Figma to the Flutter code.
- Role
- End-to-end, solo and authorial creation: product, design system and the orchestration of the AI agents that wrote the code.
- Goal
- Build a better training app than the ones I used, connecting coach and student, and learn Flutter along the way: it is my first native app.
- What I did
- I created the AI that helps the coach build workouts. It reads the student’s history and the health condition they share, only suggests load when there is training history, and refuses diagnoses, medication and diets. Every draft goes through the coach’s review before it reaches the student.
- I also created an AI for people who train without a coach. The student chats with it and it builds the workout, with the same health guardrails; anyone who already has a plan from their trainer can import the PDF or paste the text. Nothing saves on its own: the workout only goes in when the student accepts the draft.
- I built an integrated design system: the code is the source, and Figma is one of its layers. It has more than 130 components, from base pieces to charts and full screen compositions, on top of 127 tokens. The documentation is generated from the code, a catalog renders each component on mobile and on wide web with the same code, and a test checks that Figma uses the same token names.
- I’m not a developer. The code was written by AI agents I created and orchestrated, with guardrails for security, privacy law and code quality. I launched the app and keep adjusting it from real use: in October 2026, 3 coaches and 17 students use Maestro.
Design system — Figma · App — Flutter and Supabase · Code — Claude Code
Launch video
On the phone
Student and coach · 5 screens
On desktop
Coach dashboard · 3 screens
Process
From the design system to the app