 Dashboard.png)
Sweaty is a mobile-first application that focuses on connecting users to active people or groups within their city for whichever exercise or sport of their choice.
End-to-End
UX Designer
Full Stack Developer
iOS, Android, Web
Figma, Trello, ChatGPT
Laravel, Tailwind CSS
Many have found it hard to find and get connected with people/local communities that live a similar active lifestyle. According to some studies, people who do not exercise within a community are shown to be less active as well as more lonely compared to their peers that live an active lifestyle within a community.
To gather information to best understand the user, interviews and surveys were conducted. Notes and documentation were very present, despite being informal in approach. Various demographics were interviewed, then condensed into a few User Personas to best understand pain points and goals of these potential users.
After conducting interviews and surveys, [potential] users expressed that they've felt more motivated and more energetic while exercising with another like-minded partner(s). Pain points included:
• No options to view a list of exercise clubs.
• Hard to join exercise communities on social media.
• Finding exercise communities on social media is tedious.
Prior to designing wireframes, I've kept in mind the users that may be limited by their disability. To combat this, I've incorporated WCAG guidelines within the design system and components.
After really understanding the users and potential users, conducting interviews, and iterating, I've created the initial MVP solutions to best fit users' current needs.
 Group Page.png)
 User Page - Requestor.png)
 Message Page.png)
 Message Page - Chat.png)
Be flexible and nimble as possible. When a project has never been done to the same capacity new concepts may have to be made. I had to learn to stay nimble and flexible because the needs for users grew as more features and concepts were introduced.
As the interviews and user personas were being made, more issue arose where a feature had to change because it was no longer a need for users as initially gathered. I've had to be able to not marry an idea or thought process and pivot to what best fits the users' needs now, rather than a need a user will have in the future.
