Triathlon Training App UI Design -- 2

Profile We are looking for a strong independent Product/UI Designer focused on consumer mobile products, ideally with around 3–5 years of experience. Seniority is secondary to portfolio quality: the right person should have excellent visual taste, strong mobile product instincts, and evidence that they can turn complex product logic into a simple, polished experience. This should not be a broad “UI/UX + graphic designer” generalist. The ideal profile is a product designer with unusually strong visual craft, plus enough brand capability to establish a lightweight T0 identity and create a simple logo/wordmark/app icon. Experience preferences: 3–5 years is acceptable if the portfolio is exceptional. Consumer mobile work is strongly preferred over SaaS/dashboard-heavy portfolios. Fitness, wellness, lifestyle, fintech, travel or subscription-app experience is a bonus, not a requirement. Shipped product work matters more than conceptual Dribbble-style screens. Skills to prioritise 1. Visual/UI craft — highest priority. Strong typography, spacing, hierarchy, colour, layout and overall visual taste. 2. Consumer mobile product design. Ability to design native-feeling mobile experiences and make flows feel simple. 3. UX and interaction thinking. They should challenge weak flows, reduce cognitive load and improve the experience rather than simply make wireframes prettier. 4. Design systems. Strong Figma components, variants, variables/tokens, reusable patterns and component states. 5. Figma execution and handoff. Files must be clean, structured and practical for engineering implementation. 6. Lightweight brand capability. Comfortable establishing colours, typography, visual language, logo/wordmark and app icon. 7. Startup collaboration. Comfortable working directly with founders and engineers, moving quickly and designing without a large product/design team around them. 8. Illustration/drawing ability is a bonus, not a hiring requirement. Scope of work The objective is not to design every possible T0 screen. It is to establish an excellent visual direction, design the critical beta journeys, and create a reusable design system that Darcy can extend during implementation. Core deliverables: Visual direction • 2–3 visual directions explored across a small set of representative T0 screens. • One final agreed product direction. Core product UX/UI • Onboarding flow. • Today/home experience. • Weekly training plan/calendar. • Workout detail and workout states. • Completed/missed/moved workout states. • Adaptation/rescheduling experience. • Key supporting beta screens such as race/event, profile/settings, integrations and essential loading/empty/error states where required. Design system • Clean, editable Figma source files. • Colour, typography, spacing, radius, elevation and layout foundations. • Semantic Figma variables/tokens rather than disconnected hard-coded values. • Reusable components with meaningful variants and states. • Core T0-specific components such as workout cards, activity tags, navigation, inputs, buttons, sheets/modals, alerts and calendar/training components. Lightweight brand identity • Primary logo/wordmark. • Simplified logo mark/app icon. • Colour palette. • Typography system. • Basic visual/graphic language. • Simple usage guidance inside Figma. Engineering handoff • 1–2 working sessions with Darcy covering components, behaviours, edge cases and implementation questions. • Optional small ongoing allocation during implementation for unresolved UI decisions. What we will NOT pay the designer to produce unless included cheaply: • Long-form brand strategy decks. • Large brand-guideline PDFs. • Exhaustive developer specification documents. • Manually maintained Markdown design documentation. • Social/email asset libraries before the product system is established. AI / Markdown requirement Figma should be the design source of truth. The designer should structure variables, components and naming cleanly enough that T0 can translate the system into machine-readable Markdown documentation afterward. We can produce files such as design-system.md, colors.md, typography.md and components.md ourselves using AI. The designer does not need to manually maintain duplicate .md documentation. We’ll work in quick cycles: daily Slack check-ins, twice-weekly review calls, and annotated feedback directly in Figma. If this sounds like the kind of sprint you enjoy—high ownership, clear scope, plenty of creative freedom—let’s talk.