Healthy 365

Research context: everyday health competes with everyday life

The published account describes an app whose tracking, device synchronization, and information-heavy interactions made routine engagement difficult. The strategic challenge was to support everyday choices, not simply add more health measurements.

The public research considered life events, motivations, constraints, routines, and existing tools. Its reported interviews with 60 Singaporeans span younger people, working adults, parents, and older adults. Interview topics included health goals, influences, weekday and weekend routines, spending, device use, and experiences with the service.

The synthesis links competing career and family priorities to difficulty maintaining healthy habits. The opportunity is to offer relevant, feasible actions at different life stages rather than assume that every citizen has the same time, confidence, or goals.

From research themes to a product direction

The published approach moves through understanding, definition, exploration, and creation. It combines stakeholder alignment, journey synthesis, market context, concept exploration, and citizen feedback before shaping the product roadmap.

First jobbers, parents, and established or retired adults are considered as distinct contexts. Social encouragement, family-oriented knowledge, and accessible guidance are different responses to a shared need for support that fits daily life.

Concept exploration moves from a broad set of possibilities to more tangible prototypes. The reference reports focus-group evaluation and individual refinement; participant counts and results are not independently verified here.

My role: leading UX over 2.5 years in Singapore

I worked on the Healthy 365 app for 2.5 years as a Lead UX Designer in Singapore. This portfolio entry situates that experience within the broader product story while keeping publicly reported team research separate from my confirmed role.

The design discussion below explains the published experience and its rationale. It does not turn another designer’s first-person account into claims about my personal research, workshops, or individual ownership of the reproduced screens.

Architecture that supports a recurring health routine

The published foundation connects onboarding, a health overview, device pairing, and rewards. Together these create a recurring cycle: enter securely, understand current progress, capture activity reliably, and see the value of continuing.

The health overview prioritizes relevant information rather than treating all features as equal. Events, challenges, and metric views use related templates, making different activities feel like parts of one product.

The annotated journey earlier on this page is an original simplified explanation of that experience, not a pixel-for-pixel reproduction of the published information architecture.

Design the states, not just the ideal screens

Onboarding accounts for new and returning users, verification, and error handling. The important design distinction is between entering the service for the first time and resuming a known health routine.

Device pairing needs comprehensible steps and recognizable progress. When activity data is delayed or a tracker is unreliable, the interface must communicate the state instead of leaving people to infer whether their effort was recorded.

Rewards connect progress to a next action. An understandable path from activity to reward is more useful than a visually prominent points total with no explanation of what it means. These are interpretations of the documented design direction, not new usability findings.

A shared foundation for delivery

The published design system brings basic styles, reusable components, and core templates together. Its value is operational as well as visual: teams can discuss states and variations through a shared vocabulary.

The account describes design–developer collaboration, documentation, story kick-offs, and regular showcases. Remote work during the pandemic added coordination constraints, making clear decisions and reusable patterns especially important.

This material describes the wider team’s delivery approach. It is not a personal claim about which meetings Abhishek ran or which components he authored.

Launch claims, continuing constraints, and responsible reporting

The public account describes launch and continued delivery, alongside tracker reliability, data integration, security, migration, and prioritization challenges. Launch is framed as the start of an ongoing service rather than the end of the design work.

The source contains inconsistent launch dates and usage figures between its introduction and launch section. For that reason, this portfolio does not repeat those dates, adoption percentages, or daily-use figures as verified outcomes.

The defensible takeaway is the documented design direction: a more coherent health experience supported by core journeys and a shared design foundation. Causal health improvements or individual business impact cannot be established from the reference alone.