Where the design community meets.
Founder and CEO of Flawless App. Designer + Developer Joined almost 2 years ago
The first version was usable which is the criteria for the MVP really. After that, we move forward and after 6 months we made the product really stable.
Thanks to the input from our users we understand missed parts and delivered on them. The biggest things are: - An ability to collaborate with the team members, commenting live apps together. - Structure feedback in projects instead of infinite feed of screenshots - Increased quality of the AirPlay stream and streaming using a Lightning cable
When building a product it’s always good to remember that as a small team you can’t focus on everything at once. This step-by-step approach allowed us to come to the place we are right now with the product. And even tho we have a lot of thing on the roadmap and ahead – we’ve already achieved a lot.
Of course, all of that would never happen without the dedication of our users and the support from the community. Thanks to them we can keep improving the product and making feedback process easier.
We made few clickable prototypes, shared it with 20+ designers (if one of them are reading it now, know - we love you!). In 2 weeks we changed 5 or 6 design iterations before actually building anything. By making this constant prototype-feedback-improve cycle we saved ourselves a lot of time.
Thanks to this initial feedback from early testers, together with our engineering team, we were able to deliver first working MVP in a month or so.
To keep the pace going we have set a goal to deliver product release every Thursday. The concept called release train when everything you’ve implemented during the week is going “with the train” straight to the users.
After 3 months of such iteration and improvements, we had the first alpha. And sure enough, our great users have reported and requested 100+ new features which we have gladly added to our roadmap.
I’m so excited for today’s Flawless Feedback 2.0 launch!
We all know how hard it is to give feedback over live mobile applications. You can’t simply create a screenshot on your laptop, you can’t really collaborate on those screenshots and the whole thing is just tent to disappear in Slack messages.
Back during winter 2019, after talking to numerous product companies and mobile agencies we’ve noticed simple patters – in 99% of mobile companies, designers/QAs/Project Managers leave comments on the real mobile application. By making screenshots on the phone, sending those screenshots to the laptop, annotating and sharing all of that using Slack…
Well, I and my team saw a way we can improve it!
"Don’t think features, think user needs." - cool
Thanks for the feedback, Perttu!
Oh, I see. At first, I was thinking you're talking about the leaf, our logo. Now I see you mean logos of design companies. Yes, 100% agree, that's a great suggestion. That's definitely something that can be improved in future aminations.
Congrats to all your team
Now about my design process:
1) Content As you can imagine the biggest problem of putting this together was the amount of content we had. 4 years of research turned out to be quite a lot of information to fit into one website. We've tried different approaches and ended up on structuring content with 2 layers navigation.
There are 8 main topics (like "Free Design Resources" or "Managing community efforts"). For each of these topics, available information is grouped by the tool of interest (Sketch, Figma InVision Studio etc.). So as a first step, the user selects the tool. Once we know the tool we show the sub-categories related to a specific topic (like "Free Design Resources") along with visual examples.
In the end, the design consisted of 64 separate pages of content + empty states and other utility information.
2) Visual Style This time I've tried to stand back from the regular website style we use in our other products (like Flawless Feedback or Design Tools Weekly). Instead, I've decided to go with vibrant, high-contrast gradients and dark background.
It turned out to be rewarding to drop everything I used before and just sit with a pen and paper to come up with something new and fresh.
3) Branding This part was particularly tricky. The website itself has no standard logo. But still, we had to come up with the proper representation of the project. After numerous variations and tries the main association chain was developed:
‣ The project is about community ‣ Community is about people ‣ The community must be grown ‣ Building community means growing it ‣ Trees and leaves could be a representation of growth in nature ‣ The leaf has its own lifetime and growth cycle as well as community ‣ Leaf requires care to be grown as well as community ‣ Care about growth means love ‣ Love represented by the heart ‣ Community is always diverse and should be accessible for anyone to participate ‣ Community is never static and constantly changing
As a result of such thinking I've come up with the logo, which is: ‣ Tree leaf which has a form of heart ‣ It has vibrant color as a representation of diversity. Leafs could be different, not just green. ‣ The leaf has holes here and there as a representation of the dynamic nature of communities.
I really hope you enjoy reading the research and hopefully, you can find something useful for building your own community!
I'd love to explain a bit about branding we use for this project.
Since we started working in design & development industry we started taking notes on how other companies grow their communities. The website itself is full of real-life examples and interactive elements. We put a lot of effort to make sure it stands out, considering the amount of content we have there.
I do hope, that everything is perfect ;)
Good news! Probably we can expect more innovation from Sketch team ;)
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.