#quboledesignteam is embedded into persona specific verticals. We are responsible to cater to the needs of the people we are designing for while also looking at the larger picture — the platform as a whole.
Ok, this is how most of the design teams intend to function. But do we spend enough time tackling the issues faced by the people we are designing for? Or are we overwhelmed by just fighting design inconsistencies?
Who is it for? and Why?
Are you worried that your specifications didn’t get translated into the perfect pixel? Is that button of the right color and at the right place? Designers need to be at the top of their game when it comes to making sure that their work is not diluted in the implementation phase.
Design Systems allow products to scale rapidly through effective inter/intra team collaboration and reduced time to market while maintaining quality and consistent user experience. This article from here on will help you successfully productionalize a design system. I will also dive deep into the process of creating a design system, from ideation to implementation.
To ship and the way forward
We know that the products are getting bigger in size, and more complex at the same time, therefore, the design is also becoming more complex in such projects. We need stable governance sitting right in between as the core for design management during the process of building a product. And here is what the Qubole design team believes.
You can’t innovate products without first innovating the way you build them.
The design system is more than your UI kit, it’s about bringing culture and design language in your organization.
Drive user engagement for QDS via email. Currently, out of the 100,000 emails (only system generated automated emails, see scope for details) we send every week, just about 40%1 get opened by a user and just 0.02% get redirected to Qubole by clicking a link.
That amounts to about 20 emails every week lead a user to QDS even though there is a call to action in most emails.
Removing clutter on the header. Categorizing important support and help systems at one place and hence enabling better recall.Bringing the flair of personalization for users as well as the customer.A new idea to learn Qubole to activate users and drive usage.Designing in a way that the system is scalable for future needs.
An inside look at what goes behind building a side project.
Let’s start with a question. Do you think that having all the technical skills, and complete design and process knowledge is a requisite to build a product?
Well, let me just put it out there. You don’t always need to have all the skills beforehand to build a product that works. And I have a solid example to show you. Presenting Culrs!
Why a Desktop/Mac app?
I believe in working out of sheer passion, where we build and ship a product live, and work continuously on iterating this Side Project.
There were several ways to go ahead with Culrs, such as a plugin for sketch, figma, etc. Since it’s a small team of 3 who are parallelly learning the art of development and building this, we focused on creating something which sits on top of all and can become a part of your daily work life, and that had to be a desktop app.
What does our Mac App bring?
We are still the same, but new! We reimagined our Culrs web app into a mac app to simplify and accelerate the process of choosing colors for your design. Easy to access with the shortcut ⌘+E, this app sits in your mac menubar with all the color palettes you loved on our web app, ready for whenever you need it. Choose any palette from any of the categories, like Monochromatic, Tetradic, Triad, or Analogous for your design.