What this prototype is, and isn't

This is a designed walkthrough, not functioning software. Every screen is hand-built static markup intended to make the product tangible enough to react to. It exists to support partnership conversations (notably with Instafit246), gather feedback from trainers, and scope a build team. It is not a clickable app and the buttons do not do anything.

The current arc follows one persona — Aisha, a 14-day tourist from London — across client mobile, trainer desktop, and a new herbalist practitioner role. Long-term member and seasonal (Crop Over) flows are queued for a later iteration.

New in v3.3

• Sign-up & intake flow. The front door, now chapter II. A four-step shape shared across all tracks: the hook (four goal cards with honest one-liners), track-dependent quick-select (tappable, never typed), an honest readiness filter ("when do you want to start?"), and an optional-skippable starting-point screen, ending in a handoff to a real trainer rather than more questions.
• The four emotional hooks. Tourist Training, Weight Loss, Strength Building, Full Health Management. Goals are the hook; the routing to tourist / seasonal / long-term machinery happens quietly in the steps after.
• Care rails on sensitive inputs. Photos, weight, and measurements live on a single optional screen where skip is the prominent path. The weight-loss quick-select avoids "lose 10 lbs" as the lead option, framing numeric targets as something set with the trainer. Photos are client-owned, trainer-visible only by permission, herbalist-visible only if explicitly granted.
• The readiness filter. "When do you want to start?" protects the trainer's time without a wall — people self-select by saying where they are. "Just exploring" routes to a preview with no trainer assigned. A trainer only enters once readiness is proven (asking a real question, or committing through intake).
• Account timing and equal burden. Account creation comes after four taps of investment, when conversion is warmest. Full Health Management feels no heavier at intake than Tourist — it unlocks more after commitment. The only upfront difference is the optional "add a herbalist" care-team step.
• Tourist date capture. The tourist readiness step collects arrival and departure dates, since the entire tourist value proposition depends on knowing the length of stay.

New in v3.2

• Aisha's trip zine. The client-side progress view for the tourist persona. Long-form scrolling mobile layout shaped like a small travel publication — drop caps, pull quotes, a hand-drawn map, day-by-day log entries that fill in as the trip unfolds. The same view evolves: living document during the stay, looking-back-fondly piece on day 14. Marcus is present throughout as a person who was there, not as the platform's voice.
• Renée's long-term progress view. The client-side progress view for the long-term member. Concrete by default — last month vs. this month, exercise charts, muscle-group bar chart, lifetime fitness goals against the milestones she set with Marcus on day one, and quarterly check-ins on her broader "feel strong at fifty" health goal. Plateaus and difficult moments are paired with a note from Marcus before she sees them — the data is hers, the interpretation of harder moments is collaborative.
• "More views" library. Optional dashboards Renée can toggle on (isolated exercise progress, muscle-strength balance, monthly time-stamps, resting heart rate, body composition). Off by default. Nothing is pushed; she opts in when she's ready.

Two clients, one skeleton

Aisha's zine and Renée's progress view share the same underlying components — a header that announces the time horizon, a "current state" summary at the top, a series of data sections, a closing moment that points to what's next, and a consistent navigation pattern. The visual treatment of those components is radically different because the two clients are at radically different moments in their relationship with training. Aisha is on holiday and her view is a souvenir; Renée has been training for fifteen months and her view is a working document.

This is the point: the same product can hold both, because the structure underneath is shared. A future "self-training" or "athlete" persona would draw from the same skeleton with its own surface treatment. Vacationer is the warm, expressive end of the spectrum. Long-term is the calm, informational end. Both are honest to the people they serve.

New in v3.1

• Trainer's client-progress dashboard. A per-client deep read, not a roster roll-up. Renée Marshall, a long-term member at week 12 of a strength block, carries this view. Strength curves (deadlift plateaued, squat and bench still climbing), a 12-week attendance grid, session-mix donut, and two subjective trends — RPE that Marcus enters and a daily wellness check-in Renée has opted into.
• "What Lime sees" observations panel. Three plain-statement observations followed by a question — never a recommendation. The platform notices; the trainer interprets.
• "What some trainers do here" cards. Soft, Amazon-style recommendations drawn from anonymised network patterns. Framed as "what others have answered," never as what Marcus should do. Percentages are illustrative.
• "Ask Lime" — optional, after the data. A quiet input field after everything else, with four example prompts. Marcus drives what gets surfaced; Lime never volunteers prescriptive insights up front.
• Editorial charts. Thin-stroke SVG line charts in teal, with coral reserved for the plateau callout. No glowing dashboard aesthetics. Serif numerals for headline figures, italic Fraunces for axis labels and section eyebrows.

New in v3

• Goal pacing on the client dashboard. Aisha's home screen now shows direct, math-honest pacing for her stay goal ("To hit your 12-session goal, train Thursday and Saturday"). Behind pace turns coral; on pace turns teal. Process-based goal for the tourist persona; longer-stay clients would get body comp or strength milestones instead.
• Progress planning for trainers. When Marcus plans Aisha's next deadlift, Lime suggests two branching paths — conservative (+5 lbs) and progressive (+10 lbs) — with the criteria for each clearly stated. Marcus chooses, edits, sends. The platform supports the call; the trainer makes it.
• The herbalist as a separate role. Bush medicine prescription is gated to a practitioner role (Esme Pinder, placeholder). Marcus can suggest but not prescribe. Library is regionally localised — Bajan here, Trini or Jamaican in those markets. The boundary protects both trainers and clients from medical claims neither party is qualified to make.
• Editorial sidebar. Reframed as five chapters in a walkthrough rather than a generic feature list. Roman numerals in italic serif, coral accents, chapter framing borrowed from print publication.
• Sharing metadata. Favicon (teal dot), Open Graph and Twitter card tags, OG image, and meta description. Previews well in iMessage, LinkedIn, WhatsApp, Slack, X.

What's placeholder

• Renée Marshall's progression data. All 12 weeks of lifts, attendance patterns, RPE, and wellness scores are fictional but internally consistent. The plateau on deadlift is a deliberate narrative hook for the "what Lime sees" panel.
• The trainer-network percentages. "41% of trainers" and "22% of trainers" are illustrative. A production build would need a real cohort to draw these from — and would need to be careful about what gets shared, anonymised, and surfaced as a pattern.
• Esme Pinder. A placeholder name for the herbalist persona. Bajan-feeling but invented. Replace with a real practitioner you know — or step into the role yourself given your herbalism training.
• Pricing throughout. The $35 BBD per session, $25 group rate, $45/month remote training, and load increments (95→100→105 lbs) are illustrative. They have not been pressure-tested against local willingness-to-pay, trainer-margin math, or Aisha's actual training history.
• The bush medicine library. Items are real Bajan traditions (lemongrass, soursop leaf, aloe, cerasee, sea moss, bay rum, black sage), but the library is a starter list, not a vetted clinical reference. A production build would need an actual practitioner to authorise its contents.
• The Caribbean food library content. Items mix Bajan (cou-cou, breadfruit, callaloo) and broader Caribbean (pelau, doubles). A production build would structure the library by island and region.
• The "142 Lime-curated workouts" figure. An invented number. The deeper question — how much content Lime curates itself vs. enabling trainers to publish into shared collections — is unresolved.
• The workouts themselves. No proprietary sequences from Instafit246's trainer are used. Workout names and structures are generic.
• The "Keep training from London" subscription. Strategically interesting model — turning tourists into remote subscribers — but pricing, revenue split, and product depth are all open.

What's intentional

• Three client lifecycles, designed in from day one. Long-term, seasonal, tourist. The dashboard, billing, and retention flows differ per archetype. Tourist is shown here; the others are queued.
• The herbalist as a gated role. Plant medicine in a fitness app is a real differentiator and a real liability if done badly. Separating prescription from suggestion, gating it to a qualified practitioner, and keeping the library scoped to traditional everyday remedies (rather than condition-specific dosing) keeps the feature honest.
• Direct language with clients on goals. No softening: when she's behind pace, the platform tells her exactly what to do. Caribbean trainers can warm the tone in their messages; the dashboard itself stays clear.
• The trainer's judgement remains central in progress planning. Two suggested paths, not one auto-applied recommendation. The platform earns its keep by surfacing both options clearly with the criteria for each — Marcus decides.
• Multi-currency from the start. Prices appear in $BBD; EC dollar, USD, and JMD would be handled at build time. Local payment rails are a differentiator, not a roadmap item.
• Trainer is the primary buyer. Gyms come on as multi-trainer accounts. Marcus's content and clients travel with him; Lime does not disintermediate the trainer–client relationship.
• The brand "lime." Drawn from Caribbean liming — gathering with your people. Reframes fitness away from gym-grind toward community and rhythm. "L!ME" with an inverted exclamation is held as a possible refinement if competitor collisions emerge.
• Editorial aesthetic. Fraunces (serif) for display, Manrope for body, warm sand background. Aspires closer to Cereal Magazine or Aesop than to a typical fitness app.

What's queued

• Gym-admin multi-trainer view, with mentorship. Held intentionally for a later session. The thread to pick up: how head trainers or gym admins see their team's coaching patterns, support newer trainers, and develop the next generation — using the same "what some trainers do" substrate the client-progress dashboard now lays down.
• Crop Over 12-week seasonal arc. Date-targeted programming, pause/resume membership, the seasonal retention model.
• The self-training persona. A client without a trainer — different relationship to the data, different role for Lime's observations. The shared-skeleton approach should hold; the surface treatment is the open question.
• Herbalist's prescription editor. The view shows Esme's overview, but the actual prescription-building interface (what she sends to a client) is queued. Worth designing carefully given the safety considerations.
• Build team scoping. Team composition, cost ranges, and phased delivery plan. Held until the design direction is firmer.

Credits

Designed and built as a working prototype by Social Impact Design Studios in conversation with Instafit246. Workout sequences and proprietary content remain the property of the Instafit246 trainer. The persona of Marcus Hinds is a stand-in for the real trainer; Aisha, Sasha, Demi, and Esme are fictional.