DROPS Launch

  • The Ask

    Increasing application downloads by 10% by the end of Q4 2024 was the task. With the concept for DROPS already established, my team was responsible for mapping out the testing strategy, prototyping framework, and future fulfillment plan. The hand-off to development for the first iteration was five weeks out.

  • The Solution

    Compiling available user oriented data revealed areas where improvements could be made. Our hypothesis was that this new DROPS functionality should be front-and-center in the interface.

    Stakeholder meetings reflected our thoughts, we proceeded with repetitious A/B testing, user testing and competitive analysis to determine our path forward.

Due to NDA restrictions the client has requested that discovery and presentation materials are not shown.

Beneficial feedback from unmoderated usability testing on Lock Screen

Timing allowed for unmoderated user testing, which resulted in valuable feedback that led to improvements, simplifying the interface. We learned the following areas needed attention:

1- Visual countdown behind product redundant

2- “… left for drop” excessive with inventory bar

3- Title of item unnecessary after drop

4- Users unsure of specialty status of item

Dynamic Island discovery sessions improved usability & complicated Engineering efforts

Valuable improvements were made in discovery as iterations continued. Simple gestures increase details for users, focusing their experience by eliminating guesswork. Gestalt design theory flex.

1- Detailed & personalized time target for purchase

2- Inventory bar color improving visual status indicator

Internal feedback generates business needs that define iterations

Following the launch, gathering new data, additional business needs and opportunities for user-oriented improvements were identified. This ongoing analysis allowed us to redefine our objectives and enhance the product, ensuring it remained aligned with both business goals and user expectations.

  • Developed option without inventory bar to satisfy HOT badge sales with a low-inventory

  • Stale state versions were generated to satisfy “failed-transmission” needs