Yeehive
Yeehive is an up and coming startup, an incredible tool for buyers that are looking to team up to get the best price on goods and services.
First, I created the branding and collaterals. Check out the brand concept brief to see how that was conceptualized.
Next, I designed and built the welcome page in Sveltekit. You can check out the Figma file here. to see the initial concept and how it evolved as it was built.
To supplement some marketing collaterals and provide a little clarity to pur pitch market, I wrote, storyboarded, and directed the production on the explanation video which you see at the top of the site. I wanted the video to feel like it was truly a part of the design in the page, rather than dropped in as an embedded artifact, which is why nothing comes from the edge.
Everything fits seamlessly into the page, and feels like it sits among the html elements. I am very proud of this production and looking forward to extend this aesthetic across new collaterals.
The MVP
I designed and built a MVP to prop up the concept. The first iteration kept things fairly simple, just to pass along the concept and get some buy-in from stakeholders.
First I started mapping out the Buyer flow. I still need to map the vendor flow, payment exchange, and others.
I created a few loose mockups of the MVP to inform the build as I worked with a backend engineer to prop everything up. He took care of the backend services and authentication and I did all the frontend work and styling.
We had a working prototype of the app, but it seems to be broken now 😢.
The New App
I learned a lot from the initial build in regards to the UI / UX, so the next step was to setup for a proper v2 release with a more stable release and visual pattern. That meant starting on a component library as part of the bigger design system. I did an audit of the MVP to see how to atomize the pieces into components and started a new UI design aesthetic.
I have started rebuilding the application in Sveltekit as a demoable versiotn using some prepoulated JSON data. My plan is to use zsessiopn storage to create and persist a JSON flat file for the specific user. Its nothing that would be truely functional, but a easy lightweight way of walking stakeholders through the application and vet the full user flows. Hopefully thats coming soon, but if you want to see if sooner, send me an email.
I get by with a little help from my friends.END