back to home

Neighborly

Designing a mobile app user experience for an up and coming food delivery startup

Role

UX/UI Designer

Timing

Part-Time
3 Months

Tools

Figma
Illustrator

Type of project

Personal Project

overview

250 Marin is a modern, 30-floor high-rise building located in Downtown Jersey City in New Jersey, US, and their team asked me to design an experience for its residents that unifies all services and spaces offered by the building into a consolidated and easy-to-use application.

They’ve been using a competitor for quite a while, however, have grown dissatisfied with its features and want to engage with their residents more.

design process

Discover

Foundational Research
Competitive Analysis
Interviews
Branding Brainstorming

1

Define

User Persona
Surveys
Empathy Map

2

Ideate

User Flow
Informational Architecture

3

Design

Branding Crystallization
Design System
Hi-Fi Prototype

4

Discover

Foundational Research

As part of my discovery process, I’ve been in many long conversations with the management, trying to understand their perspective, goals and pain points, as well as their perception of how residents feel and think. We’ve reviewed the data on their current residents. These insights have gave me a deeper understanding of the challenges and pain points faced by the management team at 250 Marin.

Armed with this valuable information, my focus has shifted towards crafting a user-centric design strategy that not only addresses the identified pain points but also aligns with the management's broader goals. This collaborative approach ensures that the upcoming solution not only enhances resident satisfaction but also contributes to the strategic objectives and long-term success of 250 Marin.

Competitive analysis insights

Subsequently, I dived into the industry and looked at applications that are already solving a similar problem for apartment building management teams and their residents. Here's a few insights that I extracted:

Insight 1: Competitors in the industry generally offer a long list of features and are oriented at serving the lowest common denominator, rather than more tailored experiences for each client.

Insight 2: The majority of applications have outdated User Interface design

Insight 3: Only 30% of reviewed competitors had a robust community-building platform implemented.

1

define

User Persona

It was important to us to consolidate all of our research findings into a persona that we can use to empathize and think through lens of, when we work on the product. The following is what we devised:

Jessica's Pain points

  • Limited Community Engagement
    Jessica desires a stronger connection with her neighbors, but the current software lacks engaging features for fostering community interaction.
  • Payment Discrepancies
    Payments are not integrated with 250 Marin's current software and are hosted in a separate platform. Jessica doesn’t like having to login to two separate services.
  • Lack of Amenity Information & Reservation Functionality
    Jessica faces challenges when planning gatherings in the building's outdoor areas and due to the absence of a reservation system. A comprehensive feature set should include easy access to information about amenities and a reservation functionality.
  • Limited Community Engagement
    Jessica desires a stronger connection with her neighbors, but the current software lacks engaging features for fostering community interaction.
  • Limited Community Engagement
    Jessica desires a stronger connection with her neighbors, but the current software lacks engaging features for fostering community interaction.

250 marin team's Pain points

  • Community Engagement Metrics
    Current software lacks engaging features, leading to limited community interaction. The team recognizes the potential of robust community engagement as a competitive advantage in sales over local competitors.
  • Payment Management Inefficiencies
    Separation of payment services from the building's software creates inefficiencies and added workload. Managing two vendors with different operational processes has been a source of complaints from residents, impacting operational efficiency.
  • Amenity Reservation Challenges
    Absence of a reservation system for amenities poses operational difficulties. Coordinating outdoor space usage becomes complex, risking resident dissatisfaction and affecting overall satisfaction with shared facilities.
  • Administrative Strain in Document Access
    Inconvenience in accessing lease-related documents adds to the administrative burden. Direct communication or manual retrieval takes time away from essential management tasks, impacting overall operational efficiency.
  • Risk of Resident Dissatisfaction & Compliance Issues
    Perceived outdated and unintuitive software may lead to resident dissatisfaction. The team faces the risk of negative feedback and potential compliance issues, impacting overall resident satisfaction and the building's reputation.

2

3

ideate

information Architecture

We kicked off the Ideate phase by creating an Information Architecture, which gave us a thorough overview of the scope and complexity of the app and gave me and developers a much clearer path forward. We've gone through a few cycles of corrections and arrived at the following diagram:

view Full IA

lo-fi prototype

Beyond the Information Architecture, we wanted to take ourselves through the flow of the app from the lens of our user persona to see what we might have missed or misplaced in the Information Architecture diagram and ideate processes like sign up, restaurant selection, order placement and more.

test lo-fi prototype

design

branding finalization

4

design system

A well-defined, development-friendly design system ensures consistency in interface components and allows for faster design and development processes. I made it .

I used Untitled UI as the foundation of the most essential components of the application and used it to build more advanced compounded cards and blocks.

view design system

hi-fi prototype

test full prototype