top of page
Samsung Health Stack - Empowering millions of people to contribute to the future of Health Care Research

NDA | Open Source | Product Roadmap | Feature Prioritization | Dev Handoff

🚀 Feature build for the 1.0 release of the Samsung Health Stack SDK. Had ownership of the Mobile features along with another designer, Lillian. (Designs not shown in this case study due to NDA, only an overview of the process)

🎯To be released to the public in June 2023. Previewed at HIMSS 2023.

Scene 21.png
Main screens.png
My Roles & Responsibilities
Research, Brainstorming features for the product roadmap, Designing features for the Mobile SDK, Collaborating with UX writers and engineers, Updating the Design System, Preparing files, and managing Jira tickets for  smooth hand-off
Me + Lillian Choi
(Product Designers)+
UX Writers +
Product Manager +
3 weeks
Figma, Jira, Confluence
ℹ️ the opportunity..
The current flow of creating a healthcare research study is not streamlined. Researchers have to use multiple applications and software to create, launch, manage, and analyze their studies.
Group 4 (1).png
💡the solution..
Samsung Health Stack (SHS) simplifies the complex and costly process of collecting participant data using devices and developing apps.
It is an open-source platform that enables developers to quickly build necessary applications and allows medical researchers to focus on their core work. Participants can trust that their data is being managed securely. Being an Android-based open-source platform, and being in the Android community allows us to reach 2.8 billion people as participants and interactive members of research apps.
Group 6 (1).png
🧐 background for this project
Following a successful pilot launch, our next goal was to build on this foundation and develop an end-to-end MVP prototype for the next 1.0 release
The Samsung Health Stack pilot launched in September (done right before I joined the team) and the demo was shown at Samsung Developer Conference 2022 in October (photo below). It validated that people were interested and that was a clear need for the product. It also helped us gain valuable insights from interested users. 
Pictured: The amazing team. Design Team + Product Manager + Samsung Korea Developer team
🗣 qualitative research
Using feedback from Pilot launch to inform the 1.0 release
We conducted post-launch interviews. They were critical for validating user needs and identifying areas for future growth valuable insights into how researchers would use Samsung Health Stack and what they would like to see in the future. Took this feedback into ideating features for MVP Phase 1.
👁 mapping out feature roadmap
Aligning on the MVP and building product roadmap
As a design team, we presented feature recommendations and then prioritized them with the help of developers, PMs, and stakeholders. We worked on these features through design sprints with Samsung Research engineers in Korea. One of the main hurdles we encountered was aligning on the MVP (Minimum Viable Product) features with stakeholders. The stakeholders came from different departments, each with their own unique requirements and goals for the project. We also prioritized based on technical feasibility.
Screen Shot 2023-02-07 at 5_edited.png
*images blurred for NDA purposes
🔍 scope
Teamed up to tackle different parts and took ownership of different sprints - Mobile App & Web Portal
Once the scope and features were fixed, we had two design sprints going on side by side to build features for the 1.0 MVP. One for the Mobile side, and another for the Web portal side. I had ownership of the Mobile side sprints, and iterated and designed features for the SDK.
Mobile App/ SDK Design Sprint
Owners: Me + Lillian
Web Portal Design Sprint
Owners: 2 other designers
🔨 building the features
I designed Profile, Login + Onboarding, Educational Content, Study Information, and Notification modules for the Mobile App
I worked on the SDK features - Profile, Login + Onboarding, Educational Content, Study Information, and Notifications (Light and Dark Mode), with multiple iterations and adding new components to our Design System along the way.
4. Convert RAW Insights to Design Mocks
5. Discuss Mocks & Finalize Variants + Conduct User Survey
6. Usability Testing   
with Prototypes
💪 the challenge
Designing for scalability and flexibility for various use-cases to fit the open-source approach.
Being an open source ecosystem, SHS had multiple different target research audiences. For the 1.0 release, the focus was on researchers at universities and hospitals. 
🔃 flows and iterations
Explored multiple flows and iterations
Brainstormed multiple flows and narrowed down the best one according to constraints, and best fit for our use case after talking to the team and developers. Example of the two final flows presented for Onboarding shown below.
🏗 hand-off
Collaborating with PM's and Korea engineering team to ensure feasibility and scalability, and smooth hand-off
Utilized Jira and Figma comments to do continuous feasibility checks with the engineering team and prepared files for hand-off on figma, with annotations, specs and requirements.
Screen Shot 2023-04-23 at 4_edited.jpg
*images blurred for NDA purposes
👩‍🎨 final designs
To be released to the public in June 🎉
The features are still in development and are set to be launched in June, hence I can't show them here due to NDA. Please get in touch :)
🏆 recognition
We were awarded the UX Design Award 2023, for our work on Samsung Health Stack.
Learn more about the project in the video.
💭 takeaways
Learning to design for strategic foresight and longterm scalability
Strategizing features and prioritizing for current vs future releases. There were a bunch of features and solutions that we came up with in Ideation. Taking into account the users, stakeholders, and developer feasibility, learned how to narrow down for current implementation as well as think about future additions.

Designing templates & modules which are flexible and scalable to mold various use cases. Since our SDK was open source, we had to design it to be versatile enough to incorporate various use cases as well as scalable for future releases.

View previous

View next

bottom of page