{"id":7272,"date":"2021-03-09T20:29:18","date_gmt":"2021-03-09T20:29:18","guid":{"rendered":"https:\/\/cheesecakelabs.com\/blog\/?p=7272\/"},"modified":"2022-10-19T20:10:50","modified_gmt":"2022-10-19T20:10:50","slug":"building-app-phase-2-product-design","status":"publish","type":"post","link":"https:\/\/cheesecakelabs.com\/blog\/building-app-phase-2-product-design\/","title":{"rendered":"Building an app with Cheesecake Labs: Phase #2 Product Design"},"content":{"rendered":"

At Cheesecake Labs, we\u2019ve created a four-phase methodology for successful app development: product definition<\/a>, product design, product development<\/a>, and product optimization.<\/p>\n

Utilizing this process ensures an app meets \u2014 and often surpasses \u2014 the expectations of our clients, their stakeholders and, most importantly, the users.<\/p>\n

In the first installment of this blog series, we explained how our first phase \u2014 Product Definition \u2014 helps set the stage for successful design and development. Now it\u2019s time to look at Phase #2: Product Design. In this guide, we\u2019ll explain how the Cheesecake Labs team approaches application UI and UX design<\/a> \u2014 and why that unique approach delivers real value to your business.<\/p>\n

Designing delightful digital experiences for your users<\/h2>\n

Phase #2 is where the pieces of your idea really start falling into place. Until now, the vision for your app has been mostly conceptual \u2014 all the evidence is there to say it\u2019ll likely work in the market, but you don\u2019t necessarily know how it\u2019ll look and feel.<\/p>\n

By the end of this phase, you\u2019ll have a clear understanding of what the app will look like, how much it\u2019s going to cost to build, how long the development process should take and \u2014 crucially \u2014 how users will interact with it once it\u2019s in their hands.<\/p>\n

Your users are our core focus during Design. A technically-great app is that and that alone. It has no purpose. For a mobile app to be a success story, the users need to love it and to want to engage with it. That\u2019s what we aim to achieve at this stage of the journey.<\/p>\n

It\u2019s worth noting that you don\u2019t need to have undergone the Definition phase of our three-phase methodology to jump straight in at the Design end. We\u2019d recommend it, but it\u2019s not essential. Perhaps you\u2019ve already done a lot of the strategic thinking and user exploration that\u2019s required to design a stellar digital experience \u2014 we\u2019re happy to pick up where you left off or bring you up to speed and fill in the gaps.<\/p>\n

At the end of the day it all comes down to mitigating risk and delivering value. Even if you\u2019re starting with Design, we\u2019ll work hard to stress-test your app idea throughout the process \u2014 our QA team will be on hand to assess the tech and our developers will be briefed and ready to take the reins.<\/p>\n

And let\u2019s say you then decide to go in-house with your development or to commission a different agency for the build, we\u2019ll still make ourselves available for briefing and trouble-shooting, to ensure a seamless transition and a successful outcome for everyone.
\n\"\"<\/a><\/p>\n

What happens during the Cheesecake Labs Design phase?<\/h2>\n

Every project, and every client, has unique needs. We might be called Cheesecake Labs but we don\u2019t deal in cookie-cutter ways of working. And that\u2019s why we always focus on what you need \u2014 not what our last client wanted.<\/p>\n

Our preference is to work side-by-side with our clients; chatting frequently within Slack and hosting key, weekly meetings to share progress, check direction, and reaffirm that the app is working for its audience. Collaboration isn\u2019t just part of our process; it is our process.<\/p>\n

That\u2019s why the first thing we do during the Design phase is to get everyone on the same page. Perhaps we\u2019ve worked together on Product Definition already and simply need to recap. Or perhaps there\u2019s a more significant alignment that needs to take place. Either way, we\u2019ll start by (re)asking:<\/p>\n

What are we here to design, who are we designing it for, and why are we designing it?<\/p><\/blockquote>\n

This holistic and unfiltered view of the product will then help us validate the ideas and ready them for prototyping.<\/p>\n

Producing wireframes<\/h3>\n

You may be in possession of a few wireframes already, but now is the time to scope out how every screen of your mobile application will be structured. Low fidelity layouts will be designed with optimal UX in mind \u2014 the colors, images, and text will all be up for debate, but we\u2019ll commit to the user experience and journey that help users complete their tasks efficiently and with delight.<\/p>\n

\"\"<\/p>\n

Are we talking about a radically new interaction or experience for these users? Then we can use our clickable prototypes to conduct a round of initial user testing if necessary. By asking potential end users to walk through the mockups performing \u201ctasks\u201d or \u201cjobs\u201d within the app, we quickly spot opportunities to alleviate confusion. Better now than when your app hits the market.<\/p>\n

This is also a great time to introduce our QA team and Tech Lead to the project. QA can spot functions that are potentially-buggy, while your dedicated Tech Lead will highlight anything that seems too good to be true. Validating the tech early \u2014 in Design and not just Development \u2014 means we know the build is technologically viable. It also saves time during the Development phase, as the QA team will have context and already know what it is they\u2019ll need to test and what is expected from a user experience.<\/p>\n

The layouts start to take shape<\/h3>\n

Next, our UI designers will start adding color and substance. For many clients, this is when things really start to get exciting, as the app comes to life right in front of their eyes.<\/p>\n

So we can work efficiently, the UI team will create elements in a design system and replicate them across the app. Your design system will combine a variety of deliverables \u2014 such as pattern libraries and style guides \u2014 to create a collection of reusable components that reflect your brand. These elements can be assembled in several ways to fit each screen, while maintaining consistency and respecting your visual brand language.<\/p>\n

\"\"<\/p>\n

We can even start discussing micro interactions, animations and any other extras your app needs. Our intention at this stage is to create a thorough blueprint of everything your application should have to be a success with its audience.<\/p>\n

Invest in Design and the rest takes care of itself<\/h2>\n

By the end of the Design phase, you\u2019ll have a representation of your app that\u2019s as close to reality as possible, without requiring a single line of code. The next step is to take it into Development.<\/p>\n

Because our expert dev team will have followed the journey of your app idea up until now, they\u2019re primed and ready to provide a seamless transition from Design to Development.<\/p>\n

The deliverables of this Design phase may vary, depending on your project needs, but they play a crucial role in defining a crystal clear brief for the developers to get started, as soon as you give them the green light.<\/p>\n

Product Design deliverables may include:<\/strong><\/p>\n