CASE STUDY

Cross-Platform Consistency
Designing a Web-Based App to Extend the Mobile Experience

OVERVIEW

I led a two-month initiative at GetGreen, a sustainability-focused platform, to design a cross-platform experience that extends beyond mobile.

Working as the sole designer alongside a small team of developers and product owners, I translated core product goals into a web-based component app aligned with the mobile experience. Through focused requirement gathering and strategic feature prioritization, I delivered a seamless, non-mobile interface that preserved usability, design consistency, and user intent—enabling individuals and organizations to take actionable steps toward sustainability, regardless of platform.

ROLE

UI Design, Wireframing, Prototyping, Usability Testing

TEAM

Product Owner, 3 Developers

DURATION

2 months

KEY RESULTS

10

MVP features shipped

200+

users in the first 2 days

900+

actions completed

BACKGROUND

What is GetGreen?

GetGreen is a sustainability platform that empowers individuals and organizations—such as cities, universities, and companies—to achieve their climate goals through everyday, actionable habits. The existing platform was a mobile app that allowed users to log in either individually or via enterprise-specific portals, enabling them to complete tasks that contribute to reducing their carbon footprint and combating climate change.

Current mobile app

THE CHALLENGE

To design a cross-platform experience that supports diverse usage contexts—such as offices, schools, and universities—while maintaining a consistent and intuitive user experience across devices.

Final design of the desktop app (Home Screen)

The Process

Week 1 & 2

Week 3 & 4

Week 5

Week 7 & 8

1. Understand Requirements
2. MoSCoW analysis
3. Requirement Definition

1. Wireframing (Iteration 1)
2. Prototyping (Iteration 2)
3. Dev discussions

1. Internal Usability Testing
2. Product Owner Review

1. Final Prototyping
2. Handoff & Support

REQUIREMENT DEFINITION

The process began with defining the MVP features for the web app using the MoSCoW method (Must-have, Should-have, Could-have, Won’t-have), in close collaboration with product owners and developers. We aligned on business goals, user needs, and key constraints.

Business Goals

✦  Drive user retention and cross-platform consistency

✦  Support B2B partnerships

✦  Expand market reach

✦ Enhance user experience

User Goals

✦  Login & Sign Up (Email & Google)

✦  View actions and saved actions, browse categories, and complete actions

✦  View Active projects

✦  View Profile

Constraints

✦ Tight launch timeline

✦  Technical limitations of a new platform

✦  No time to test with actual users (internal testing only)

DESIGN DECISIONS & ITERATIONS

Decision #1

How to display Action card details?

Decision #2

Project page

Projects represent groups within an organization that users can choose to join based on their interests. The leaves earned through individual actions contribute to the group’s overall goal. Users can browse available projects, join the ones they resonate with, and view leaderboards for each project.

Decision #3

Adding leaf confetti

In the mobile app, a leaf confetti animation celebrates each completed action, reinforcing a sense of achievement. Due to technical complexity, this was excluded from the MVP. However, during internal testing, users expressed that they missed the animation, noting a drop in satisfaction and emotional engagement.

FINAL DESIGN

Goal #1

Login & Sign Up

Goal #2

View Actions & Complete Actions

View actions

View action details

Complete action

Goal #2

Explore categories

Explore categories

Category specific actions

Goal #3

View Active Project

Active project and leaderboard

Project details

Goal #4

View Profile

OUTCOMES

The project successfully delivered a web-based MVP aligned with the mobile app, enabling non-mobile engagement in classrooms and offices. Key user needs were addressed through clear design decisions, and internal testing validated essential features, supporting a timely and focused launch.

Key Outcomes

Improved cross-platform consistency

Delivered a web experience aligned with the mobile app, supporting a seamless user journey.

Improved User Experience

Addressed a few of the usability issues in the mobile while balancing the cross-platform consistency

Accelerated product launch

Shipped a functional MVP within tight deadlines while balancing usability and technical constraints.

Metrics

10

MVP features shipped

200+

users in the first 2 days

900+

actions completed

KEY TAKEAWAYS

Designing for platform-specific contexts

Adapting mobile patterns to web taught me how to balance consistency with platform-specific needs like screen size, layout flexibility, and interaction models.

Prioritization through the MoSCoW method

Using the MoSCoW framework helped me focus on delivering core functionality under time constraints, while aligning with both user and business priorities.

Designing with limited research

With no time for user research, I leaned on insights from the mobile app to inform decisions, ensuring continuity and relevance despite tight timelines.

Cross-functional collaboration matters

Partnering closely with developers and product owners reinforced how strong communication helps navigate constraints and align solutions across teams.