Fitness and habit tracking
An example app where users log workouts and habits, keep streaks, and get coached by a premium AI feature.
Example app Built from planned modules. Not a customer. Not a supported app today.
Illustrative rule: premium AI coaching with a monthly allowance
| 1 | modules: | |
| 2 | +Added | subscriptions: |
| 3 | +Added | plans: [free, premium] |
| 4 | +Added | ai_coach: |
| 5 | +Added | requires_plan: premium |
| 6 | +Added | quota: |
| 7 | +Added | per: billing_period |
| 8 | +Added | limit: 200 |
| 9 | +Added | rules: |
| 10 | +Added | workout_streak: |
| 11 | +Added | counts: workouts |
| 12 | +Added | per: day |
Placeholder values and unfinished syntax. Not a released feature.
What is the Fitness and habit tracking example app?
A person opens the app, logs a workout or checks off a habit, and sees a streak grow. A free tier lets them track. A premium tier adds an AI coach that reviews recent activity and suggests the next session.
Examples of this category include workout trackers, habit trackers, calorie tracking, and fitness coaching. This page describes a design target. It is not a claim that Edict already supports a complete app of this type.
What backend does the Fitness and habit tracking example need?
- Authentication, so each person has a private history.
- Activity records, goals, and streaks.
- Subscriptions that decide who gets premium features.
- Notifications and scheduled reminders.
- AI coaching.
How do the planned modules compose in the Fitness and habit tracking example?
Authentication is designed to give identity, and the database to store activity records owned by the user. Business logic would compute the streak from those records and could emit an event when a streak is about to break. Push notifications would listen for that event and send a reminder. Background jobs are planned to send the daily reminder at a time that suits the user.
For the coach, Authentication, Subscriptions, and the AI gateway are designed to work together. The gateway is designed to check who is calling, check for the premium entitlement, and apply the monthly allowance. If a provider call fails, the request is intended not to count against the user.
What would an illustrative rule look like in the Fitness and habit tracking example?
The configuration above is illustrative. It shows the idea: the coach requires a premium plan and has a quota that resets each billing period. The streak rule counts workouts per day. The exact syntax and the number are placeholders and are not final.
What is example and what is planned in the Fitness and habit tracking example?
Everything here is an example. The modules named are planned and in development, and none is available today. Your own app decides the goals, the exercise types, the coaching prompts, the screens, and the pricing of the premium tier. Edict is designed to enforce the rules you state and to connect the parts.
Follow the module pages for the planned design of each part, and join the beta waitlist to hear about progress.
Questions about the Fitness and habit tracking example
Short answers about what this example does and does not claim.
Is this a real customer app?
No. It is an example category used to test the Edict design. It is not a customer or a shipped app.
Which examples are similar to Fitness and habit tracking?
These share the most modules with this one.
Get an invitation when the beta opens.
Joining gets you email updates while Edict is built, and an invitation to the hosted beta when it opens.
Building now. No launch date yet.
Join the beta waitlist
Open the signup form on KitEdict is in development. Joining does not create an account or start a trial.