In

Now that we’re done with the meat of the module and you know everything you need to know to get started, I have some bonus materials for you. Because the knowledge doesn’t end there. Theres so much more to learn about this topic and most of it can not be taught. You’ll just have to go and try it yourself to figure out how some special cases work.

Some things however are teachable and relevant for you and I don’t want you to miss out on them. That’s why I created this bonus section for you. I’ll answer a common question that I know gave me headaches when I first started out.

The question is which workflow to use and in which order to design apps. I’ll give you the shortcut right now: there is no right or wrong, there just is what works best for you.

Every person has his own workflow for developing layouts. I personally like to start from scratch and incrementally build up more complex layouts so I can see exactly what is going on and what is going wrong. Some other people love to design the whole screen for an app for a specific screen size and then, once that is done, chain everything together with constraints to make it adapt to different screen sizes etc.

I have outlined and described the 2 most important and popular workflows in this extra. Feel free to pick them apart and build your own workflow from the bits and pieces you can gain from this.

Working from a design

Most of the time we think about Apps and designing them we usually picture it starting from scratch. But what actually happens is that there are other people before us that do the designing part for us. We’re developers and while some of us might have design skills and knowledge, there’s a good chance that we are not the ones to design the app. I we are though this workflow will still make more sense.

In my mind it always happened like this:

  1. I had an idea
  2. I sat down on my computer and pulled some things out to the Interface Builder and connected them to code
  3. I implemented a functionality
  4. and then I repeated

It was this code and fix mentality that didn’t really have much of a purpose and direction to it. If you are designing your apps yourself I encourage you to stay away from working like that because it might work out great in the beginning but it will hurt you in the long run. Design the app in any Design app you like, like Sketch, Illustrator, Photoshop or Adobe Experience Design and finish all the design elements and everything you need before you move over to Xcode.

What you should end up with, or what the designer or team you’ll work with should be something like this. A mockup of the app and what it should look like. Plus all the assets of course. Each button and each item should be delivered to you in the necessary size.

Ask Anything!

Do you have any questions? Ask them! I'll answer via Email as soon as I read it.

Not readable? Change text. captcha txt
0