Connect the activity sources.
Garmin Connect synchronisation and FIT-file processing bring activity data into the application. A background worker handles recurring imports separately from the interactive web interface.
Training data.
A working foundation.
A mountain-training application connecting activity imports, preparation plans and terrain-aware route analysis. A custom workspace where the data behind training meets the context of the next route.
Inside the buildImported activity data
Worker and persistence
Web application
A training record, a preparation plan and a mountain route describe different parts of the same task. Bringing them into one application means connecting data formats, recurring imports and geographic analysis.
MERA was built as a custom platform around that workflow. Garmin Connect synchronisation and FIT-file processing feed the activity workspace, while planning and route-analysis features give the imported data a place in the product.
Garmin Connect synchronisation and FIT-file processing bring activity data into the application. A background worker handles recurring imports separately from the interactive web interface.
Preparation plans and sessions have their own data model. Plan adjustments are recorded against named rules, keeping changes traceable within the application.
Route and elevation analysis add geographic context to preparation. The application brings routes, profiles and activity information into the same working environment.
The web interface, background processing and persistent data have distinct roles. Next.js presents the workspace, a worker handles imports, and PostgreSQL stores the application data. This separation supports a product that has work to do even when the interface is not open.
Explore custom software developmentTell us about your data sources, your workflow and the product you want to build.
hello@rootdevelopment.eu