A starting point, not a ceiling.

Hybrid Training Log (HTL) is the first opinionated frontend for this idea. It reflects one athlete's approach to training. The plan is to make its repository public so you can start with something concrete, then make it yours.

A fork is your own copy of the code. You can change the navigation, replace a weekly summary, remove screens you never use, or build a different visual identity. Your app still connects through the platform's supported API.

Public repository coming soon. HTL is not available for public forking yet. The repository URL, license, and setup instructions will be added when published. No launch date is promised.

Start with what matters to you.

You don't have to start with code. Start with the question you want your app to answer. An AI coding agent can help turn that into an interface, using the frontend source and the backend's documented contract.

An example request

“Make my weekly summary show total training minutes instead of distance. Separate strength and endurance, and keep my workout history exactly as it is.”

For a swimmer, that might mean lap splits and total laps. For a runner, easy-versus-hard minutes. For someone training across disciplines, time and recorded effort could take priority. These are examples of possible views, not claims that those calculations or integrations are already shipped.

Your changes. A deliberate process.

  1. Start from the public frontend. Once HTL is released, read its license and setup guide, then create your own fork.
  2. Describe or code the change. Work on a separate version. Use the supported Training Log Cloud API instead of copying or modifying the backend.
  3. Preview and test. Check your screens, data permissions, and error states before replacing a version you use.
  4. Keep a working version. Retain your source history and a recovery path outside the app you're changing.
  5. Review upstream updates. Decide how official changes fit your version, especially when they overlap your customizations.

Android is the initial standalone mobile direction. Personalized APK builds, understandable merge proposals, and managed recovery are part of the longer-term builder concept. They are not a download service available on this site.

Change the experience.
Keep the training.

The backend owns the training-data contract. Your frontend chooses how to present it. Planned sessions remain separate from completed training; units, measurements, and record history should stay meaningful across clients.

That separation is the core idea: new screens should not require a new training history. It also means a custom interface cannot grant itself access to someone else's workouts or bypass permission rules.

Read about data ownership and sharing, or explore the platform and plugin roadmap.