Inspiration
Imagine yourself looking for the winter coat online. You found the perfect style, you decided on the color, price is great, there is even a discount! All is left to do before you can put it into the basket is to pick your size... But your size is "out of stock"!
Arrrrggg!
You decide to make a compromise and order another coat. You wait a couple of days, it arrives - you try in on… and it doesn’t fit!
Arrrrrggg!
Now you need to pack the coat, bring the box to the post office and send it back. And you still don’t have the coat!!!
Arrrrrggg!
Size Tables / Converters / Free returns are not the cure! They are just the symptoms!
Size is the moving target. It changes from season to season, from style to style, from vendor to vendor. And sometimes you change - finally decided to go to the gym?
Lazzo moves as fast as the Size!
What it does
ONE
It does all the busy work of the size converter: finding your perfect size for each country, metric system or clothing vendor.
Too simple?
TWO
Well, it goes beyond that. Lazzo shows you only the products that will fit you perfectly! Never again will you see “out of stock” message.
Too simple?
THREE
Well, it goes beyond that. As soon as product arrives - you get the push notification with the sexy, easy and fun way to give the fit score:
Perfect Fit? Turned out smaller? Turned out bigger?
You just created something amazing! You caught the Size!
Now the whole world knows that Winter Season 2016 Coat of United Colours of Benetton in the size of 48 is actually turning out smaller.
Our Community-Driven Machine Learning Recommendation Algorithm is Moving as Fast as Size Changes!
How I built it
We focused on there important aspects:
- Beautiful Design and Easy Fun to Use UI
- POLITE UI - since we are dealing with delicate topic of size
- Native iOS Application
- Node.js / MongoDB backend powering and scaling the App and the Algorithm
- Open API for others to use our Algorithm
- Pitch Website
We used:
- Sketch
- Zeplin
- Bear
- Slack
- Radix TLD
- NO Alcohol =)
Challenges I ran into
- Non-Standard UI-Elements due to our high design expectations
- Chairs were not that comfy… Sorry, guys…
- Time Constrains - often we needed to run ad-hoc crisis meeting to decide how to cut the scope to finish on time
- MVP - how much VIABLE does it need to be - to stay useful and sexy
Accomplishments that I'm proud of
Problem was clear.
We are proud we could be able to FOCUS on the lean and understandable solution.
Also, we’re pretty excited about the fact that we didn’t only use Zalando API, we also created our own!
This is our way to give back to the community.
Using our API online shops can leverage the power of our community-driven algorithm:
http://git.factory.mn/manufactura/lazzo_backend/wikis/api USER: hackjunction PASS: mG6SoVywk3u
What I learned
It was very important to learn from the Zalando guys that the problem with returns is real.
Our research showed - that it’s actually the huge problem for e-commerce - but to get the validation first-hand from the Europe largest e-commerce platform - was golden!
What's next for Lazzo
2017 Roadmap
Presenting the Lazzo at the World Mobile Congress in Barcelona (4YFN Track)
~600 k Installs by the end of the year
Our API is used in one big e-commerce platform
By the end of 2017 we want to become
The World Largest Big Data Research on the Problem of Size
And YES, we are looking for INVESTORS!
Log in or sign up for Devpost to join the conversation.