September to October 2024

This project included

This project included

UI Design

UI Design

Benchmarking

Benchmarking

Naming

Naming

Visual identity

Visual identity

Logo Design

Logo Design

Hand-off

Hand-off

Dev communication

Dev communication

Tools used

Tools used

Figma

Figma

Discord

Discord

Google Meet

Google Meet

Trello

Trello

GitHub

GitHub

Context

Context

With a diverse team from the Chingu community, a web application was developed to simplify expense sharing among friends, family, roommates, and others, consolidating expense management into a single platform. The project had a maximum timeframe of six weeks, focusing on skill-building and the development of soft skills.


Due to the diversity of nationalities, the team’s communication was conducted entirely in English.

With a diverse team from the Chingu community, a web application was developed to simplify expense sharing among friends, family, roommates, and others, consolidating expense management into a single platform. The project had a maximum timeframe of six weeks, focusing on skill-building and the development of soft skills.


Due to the diversity of nationalities, the team’s communication was conducted entirely in English.

With a diverse team from the Chingu community, a web application was developed to simplify expense sharing among friends, family, roommates, and others, consolidating expense management into a single platform. The project had a maximum timeframe of six weeks, focusing on skill-building and the development of soft skills.


Due to the diversity of nationalities, the team’s communication was conducted entirely in English.

Project start

Project start

At the beginning of the project, we received a detailed briefing outlining several requirements to be met. Analyzing these requirements made it possible to identify key pain points, which helped guide future design decisions. This approach served as an alternative to user research, which could not be conducted due to the tight deadline.


The project followed the timeline below:

At the beginning of the project, we received a detailed briefing outlining several requirements to be met. Analyzing these requirements made it possible to identify key pain points, which helped guide future design decisions. This approach served as an alternative to user research, which could not be conducted due to the tight deadline.


The project followed the timeline below:

Design process

Design process

To ensure developers had enough time to implement the application, it was necessary to start and accelerate the design process quickly, which proved to be a significant challenge. Tools such as moodboards, element collages, and user flows were used to efficiently test and define design directions.


Whenever possible, feedback and guidance were sought from the Product Owner and the development team, ensuring the technical feasibility of the solutions and helping to address potential design issues.

To ensure developers had enough time to implement the application, it was necessary to start and accelerate the design process quickly, which proved to be a significant challenge. Tools such as moodboards, element collages, and user flows were used to efficiently test and define design directions.


Whenever possible, feedback and guidance were sought from the Product Owner and the development team, ensuring the technical feasibility of the solutions and helping to address potential design issues.

Benchmarking

Benchmarking

After analyzing around 30 expense-sharing apps, recurring patterns were identified in the names and logos used by competitors. Based on this analysis, criteria were established to create a name and logo that would stand out in the market, avoiding the use of widely adopted words, styles, shapes, and representations.

After analyzing around 30 expense-sharing apps, recurring patterns were identified in the names and logos used by competitors. Based on this analysis, criteria were established to create a name and logo that would stand out in the market, avoiding the use of widely adopted words, styles, shapes, and representations.

Naming and logo

Naming and logo

A direct and descriptive approach was chosen. The term "Slice" refers to the act of cutting, symbolizing the division of expenses into smaller parts to be shared among friends or family. The logo visually conveys this concept by using a cut in the outline of a circle. As the parts move, the empty space inside the circle takes the shape of an "S."

A direct and descriptive approach was chosen. The term "Slice" refers to the act of cutting, symbolizing the division of expenses into smaller parts to be shared among friends or family. The logo visually conveys this concept by using a cut in the outline of a circle. As the parts move, the empty space inside the circle takes the shape of an "S."

Learnings

Learnings

  • Interdisciplinary communication is vital: I realized the importance of maintaining clear and constant communication with the entire team, especially with developers, to ensure alignment. I am now better prepared to communicate design decisions to developers, both in Portuguese and in English, and also to handle technical constraints more quickly and collaboratively.

  • Working with real constraints: With time limitations and requirements, prioritizing high-impact tasks and balancing demands with creativity, while figuring out how to ensure the best possible user experience despite challenges, proved to be essential.

  • Componentization and Design System development: By applying these practices, I made several mistakes that turned into valuable learning opportunities. As a result, I learned to handle and organize components more efficiently.

  • Interdisciplinary communication is vital: I realized the importance of maintaining clear and constant communication with the entire team, especially with developers, to ensure alignment. I am now better prepared to communicate design decisions to developers, both in Portuguese and in English, and also to handle technical constraints more quickly and collaboratively.

  • Working with real constraints: With time limitations and requirements, prioritizing high-impact tasks and balancing demands with creativity, while figuring out how to ensure the best possible user experience despite challenges, proved to be essential.

  • Componentization and Design System development: By applying these practices, I made several mistakes that turned into valuable learning opportunities. As a result, I learned to handle and organize components more efficiently.

Todos os direitos reservados | Leonardo Siqueira © 2024

Todos os direitos reservados a Leonardo Siqueira © 2024