Fitness Dashboard App: Charts That Drive Decisions

A dashboard is not valuable because it looks like mission control. It is valuable when it makes one recurring decision faster.

Name that decision before you choose a chart. Then ask ChatRPE to build it—as a real fitness dashboard app, not a one-time reply you have to re-request every time you want to look at it. You describe the question in a sentence; it builds the widgets, saves them under a name, and keeps them current from the same Universal Logbook your workouts and meals already land in.

Use the three-widget rule

A recomposition dashboard might use bodyweight trend, weekly protein average, and training consistency. A knee dashboard might use leg-day volume, pain score, and notes from high-pain sessions.

Try this: “Create a recomposition dashboard with bodyweight trend, weekly protein average, and training consistency. Explain what change in each view would matter.”

What a chart widget can actually show

ChatRPE's fitness progress charts are not limited to one plain line. Ask for a line, bar, area, scatter, or pie chart depending on what the question needs, and stack more than one metric on the same view—including two different scales on left and right axes, so bodyweight and weekly volume can share a chart without one flattening the other. A scatter chart is the one built specifically for two metrics that might move together—ask it to plot sleep against training RPE, or protein against bodyweight trend, to see the relationship instead of guessing at it from two separate logs.

For trend questions, ask for a moving average or trend line laid over the raw data so a noisy metric like daily bodyweight or daily soreness stops looking like static. On a chart with several series you can say which one the overlay belongs to, so the moving average smooths your weight without also smoothing your protein. For a goal you're chasing, ask for a target line so every future point shows distance to it instead of you doing the math yourself.

For anything about consistency—training days, protein-goal hits, a habit you're tracking—ask for a heatmap. It renders as a GitHub-style activity calendar: one cell per day, shaded by whether and how well you hit the target, so a six-week streak or a quiet patch is visible at a glance instead of buried in a list. This is the same view worth checking alongside the habit tracker when a habit's consistency, not just its latest entry, is the question.

Chart the number you actually care about, not the one you logged

This is where workout analytics usually stop short. The interesting number is often not a field in your log—it is arithmetic over the fields in your log, and doing that arithmetic by hand is why most people never see the chart.

ChatRPE can compute the metric as it builds the chart:

• Estimated 1RM per session. weight × (1 + reps ÷ 30) across every set of a named lift, reduced to the best set of each session. That is the top-set line the progressive overload tracker argues you should be watching, drawn from sets you logged normally—not from a separate "1RM test" you have to remember to do. The one-rep max guide covers where the estimate comes from and how far to trust it.
• Total tonnage. weight × reps summed across a session, so a week where you added reps rather than plates still shows the work.
• A ratio between two different logs. Protein per kilogram of bodyweight is two separate data types—your meals and your weigh-ins—divided by each other after they are lined up by date. Ask for it and it becomes one series. A squat-to-bench strength ratio works the same way.

Two practical notes make those work. When one input is logged less often than the other—weekly weigh-ins against daily meals—ask it to carry the last value forward so the daily calculation has something to divide by. And an input series can be hidden from the chart while still feeding the calculation, so a protein-per-kilogram view does not have to display raw bodyweight next to it.

Try this: “Chart my estimated 1RM on deadlift per session for the last year with a 7-day moving average, and put my bodyweight on the right axis.”

A widget is not always a chart

Some questions do not want a line. A dashboard can hold four kinds of widget, and mixing them is usually what makes one worth reopening:

The KPI tile is the underrated one. Give it a target and ask for what's remaining rather than the raw total, and you get "38 g of protein to go" as a number on a card instead of a chart you have to read a value off. Pair one with the running-total workflow in the protein tracker guide and the daily gap stops being something you have to ask about.

Custom cards render in a locked-down frame: styling works, but scripts, forms, embeds, and network access are all blocked. It is a way to lay out your own numbers, not a place to run code.

One-off chart or saved dashboard?

Ask for a quick chart in the conversation when it answers a question you may never ask again—ChatRPE will render it right in the reply. Ask ChatRPE to save it as a dashboard when it is a signal you plan to check repeatedly; saved dashboards live in your sidebar under "My Dashboards" and reopen with the same widgets intact, so you are not rebuilding the view or re-explaining the metric every time.

Saved widgets are not frozen snapshots. They re-read your logbook when the underlying data changes and again whenever you open the dashboard, so a chart you built in June is showing today's numbers when you come back to it in August.

Do not chart everything just because you can. Read the custom tracking guide if the metric itself needs a cleaner definition first—any metric you've logged, not just built-in workout or nutrition fields, can become a widget.

Put the dashboard on your home screen

On iPhone, a saved dashboard does not have to stay inside the app. ChatRPE's iOS app keeps your dashboard widgets available to the system widget gallery, grouped by dashboard, so you add one through the normal iOS Add Widget flow and pick which components it shows. Small, medium, and large sizes are supported—the larger sizes fit more components—and tapping the widget opens the app.

The useful part is that it updates from your logging rather than on a schedule you have to think about. Log a meal or finish a session in chat, and the home-screen view re-renders with the new numbers. A weight trend or a "protein remaining today" tile sitting on your home screen is the shortest possible distance between the data and the decision, because you see it without deciding to look.

When you want the number, not the picture

Sometimes a chart is more than the question deserves. ChatRPE can also just summarize a metric over a window—average, high, low, total, entry count, and which direction the period moved—and it can run that summary over the same computed metrics your charts use, so the estimated 1RM it quotes matches the one it drew.

Give a summary a date range and it answers exactly that stretch, which is how to interrogate one training block or diet phase at a time. The direction it reports comes from the first half of that window against the second, so use it to pick where to look, then build the dashboard that settles it.

Prune without mercy

After one or two weeks, remove every widget you did not reopen. Good analytics reduce mental load. They do not become another app to maintain.

Tie each dashboard to an action: continue, adjust, investigate, or stop tracking. A chart that supports one of those has earned its space. Ask ChatRPE to drop or swap a widget in the same conversation you were already in, in a sentence. When a dashboard has done its job, ask it to delete the whole thing; the logged data underneath is untouched, and you can rebuild the view from one sentence if the question ever comes back. The data export guide covers what leaving with that history looks like.