The problem
Music practice on a phone needs exercises, audio playback and progress tracking, with music rules kept separate from device details.
Music practice on a phone needs exercises, audio playback and progress tracking, with music rules kept separate from device details.
FretUp brings music practice activities into an app with local progress and preferences. Native features support the Android and iOS experience.
Flutter/Dart app with music rules, audio ports and progress stored on the device.
View technical details →Kotlin integration on Android for audio, timing and widgets.
View technical details →iOS extension in Swift/WidgetKit with controlled state sharing with the app.
View technical details →Project scope The offline activities and audio described here do not need an account or remote database. The website presents the product and links to the app stores.
Availability and requirements are set by each store.
Archived Android screenshots in Portuguese from the September 2026 release materials: home and note identification practice. These show that app version.


I designed and developed FretUp, from its music architecture to the Flutter app, native Android/iOS features and website. The structure separates exercises, audio playback and device features.
Music rules are separate from the UI. Audio ports control playback. Progress is stored locally.
The product combines a Flutter app, native integrations and a static website for presentation and distribution.
What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.
Music practice and local progress.
Music rules, application, presentation and audio ports separate exercises from playback and interface details.
Android-specific features.
Audio/timing integrations and widgets support the Flutter runtime. They are not a second independent app.
iOS-specific features.
Widget extension and controlled state sharing with the app.
Public PT/EN site and download links.
Python builds static pages from templates and localized content. The browser receives HTML, CSS and JavaScript.
Music rules guide app activities. Audio ports and native integrations handle the device. The website presents the product and links to stores without running music logic.
Progress and preferences are local to the device. Offline audio and activities do not require an account or remote database for this scope.
App, asset and website checks, rule tests and platform validation. Builds, device acceptance and store availability are separate steps.
Tell me what you need. The WhatsApp draft includes this project as a reference. You can edit it before sending.

Monitoring, agents and log analysis.
Explore project
Inspections and field work connected to the business.
With Alcimar Bonomi · Breno SoaresExplore project
Data and tools for cattle management.
With Breno SoaresExplore project