Peaple
PROJECT INFO
Create a mobile application that functions as a social companion helping users spend more time with the people they value most.
Role
Mobile Dev
UI/UX Design
Branding
Founder
Year
2022 - Current
Figma
React Native
Expo
GraphQL
Tech
Stream
Postgres
Apollo
Prisma
As a creative and technical co-founder of Peaple, I assumed every role in the design and development pipeline. That included brand identity, concept creation, idea validation, marketing, wire-framing, asset creation, prototyping, and of course coding and testing the actual product.
MY ROLE
Hammersmith One Regular
BRAND IDENTITY
Logo
When it comes to shape theory, it's a no-brainer to opt for curves and circles when trying to elicit friendliness, fun, and community. Furthermore, tapping into the overall image of the brand's clear running motif of 'peas' was paramount for the logo. The shading lends a little more depth and uniqueness to the logo without making it complex. It's memorable, relevant, represents the values of the company, and certainly unique.
Font
The font used throughout the brand is playful with it's curves and off-centre 'i', but ultimately it is clear and legible, which is important for a company that conveys much information through copy on the app.
Colours
Heavily influenced by peas, the three greens compliment each other and the greys are used to make sure those brand colours really pop in any instance. The white serves as a clear contrasting colour without taking away from the brand greens.
Themes, colours, layouts, navigation, features, user stories, interaction, and more were tested and iterated upon through a series of wireframes, prototypes, and surveys. Our goal was to have a clear design vision in the shape of an interactive high-fidelity prototype before launching into the coding aspect of the app.
This prototype served as both a pivotal reference resource during development and a way to show interested parties what the app will look like.
PROTOTYPING
CODING
At the beginning of this project I had barely any experience in app development. Subsequently, I had to learn a plethora of new skills in order to create a viable product. I threw myself into the deep-end and am much better off for it.
When building a stack, there are thousands of combinations. We explored many of them!
It's important to factor in efficiency, familiarity, performance, and quality. I chose React Native with Expo because I had experience with React for the frontend. For the backend I went with an entirely unfamiliar but powerful and clean structure using GraphQL, Apollo, Prisma, Postgres, AWS App Runner, and Firebase Auth. I now love GraphQL and the stack works seamlessly.
STACK
Ups and downs, clarity and confusion, defeat and relief. There's nothing quite like creating an app.
IMPLEMENTATION
Research requires evidence, and evidence can only be found in your own environment. Testing is the source of sorrow as well as pure elation entirely reliant upon console logs. Commented carcasses of testing solutions can be found throughout the app just in case they need to be revisited. Every solution has to be rigorously investigated, devoid of breaking edge-cases, and optimised.
2b. TESTING
The primary skill a developer needs is the ability to browse the web in search of literally any possible scrap of a solution in the deep depths of a Stack Overflow comment section, a 3 hour long tutorial on an adjacent topic, or sometimes a very odd looking link... I have learnt much about the ways of the wandering web nomad and am proud of my new ability.
2a. RESEARCH
Authentication, hook errors, server connection, mutation syntax, library issues, tab navigation, peer dependencies, spontaneous crashes, responsive design, the list is way too long to type out. Dealing with an entire system means that you get problems across the board and dealing with them requires a plethora of skills and abundance of knowledge which I did not yet posses.
1. PROBLEMS
My favourite type of problem is the one that I can solve on my own through the brilliance of code. Some solutions after research don't cut it. For example, the calendar view on the app is entirely custom built to suit my needs. Creating this app has taught me the importance of leveraging the community and its resources, as well as given me a platform to hone my skills as a developer when it comes to raw code.
2c. INNOVATION
No one is a one man army. A divergent opinion, a new set of eyes, and a sounding board are invaluable elements when it comes to solving any problem in development. I now understand the importance of a support network when I can't solve things on my own.
3. MENTORS
Every solution to every problem is the fuel that keeps me going as a developer. Seeing the result come to life, building something that works, and ticking off a problem on the list just makes me want to delve into the next one.
4. SOLUTION
OUTCOMES
Creating Peaple has taught me how to adapt to unforeseen circumstances, up-skill quickly to achieve goals, be resilient when faced with seemingly endless problems, leverage the support network around me, trust my work, and be proud of what I can create.
I created a small landing site for the app using Wix that showcases some features and has a newsletter sign-up.
WEBSITE
VISIT
SITE
Peaple also has a dedicated Instagram account that shows some Peas, developer updates, and more. Soon to be very active leading up to launch.
SEE
PAGE