Title is correct. The reason why there is so much push for getting designers to code is that it seems like a lot designers design things for platforms they don't understand. If you're a designer and you hand me an iOS composition or mock with a traditional web/desktop dropdown; as an iOS developer, I'm going to immediately assume you don't know what you're doing. iOS has native elements which correspond to the equivalent dropdown on web and desktop. The challenge also goes deeper than UI elements. If you're working with 2 designers and one of them understands the mechanics of the framework they are designing for; it's going to be far easier for a developer to work with them and have a conversation.
The problem is that the goto lazy answer is: "Make designers develop so they can feel developers pain" which I don't think is necesary. From a developers perspective, the challenge is more about getting designers to understand the limitations and impact of their design decisions and really good designers know this.
As a concrete example the status bar on iOS can be two colors... black or white. So if a designer is asked to build a side nav menu and they come back with a design that has a dark layout on the main view and a light layout on the side nav or vice versa, part of the status bar will be invisible depending on which color status bar you choose. There are lots of ways around this, but an example like the one below shows that the designer understands that they are picking colors where the white status bar will stand out.
Meanwhile the Mailbox app is an example where the developer would need to use private frameworks (Not recommend by Apple and could potentially get your app rejected) or screenshot capture and overlay to hide and/or move the status bar
Title is correct. The reason why there is so much push for getting designers to code is that it seems like a lot designers design things for platforms they don't understand. If you're a designer and you hand me an iOS composition or mock with a traditional web/desktop dropdown; as an iOS developer, I'm going to immediately assume you don't know what you're doing. iOS has native elements which correspond to the equivalent dropdown on web and desktop. The challenge also goes deeper than UI elements. If you're working with 2 designers and one of them understands the mechanics of the framework they are designing for; it's going to be far easier for a developer to work with them and have a conversation.
The problem is that the goto lazy answer is: "Make designers develop so they can feel developers pain" which I don't think is necesary. From a developers perspective, the challenge is more about getting designers to understand the limitations and impact of their design decisions and really good designers know this.
As a concrete example the status bar on iOS can be two colors... black or white. So if a designer is asked to build a side nav menu and they come back with a design that has a dark layout on the main view and a light layout on the side nav or vice versa, part of the status bar will be invisible depending on which color status bar you choose. There are lots of ways around this, but an example like the one below shows that the designer understands that they are picking colors where the white status bar will stand out.
Meanwhile the Mailbox app is an example where the developer would need to use private frameworks (Not recommend by Apple and could potentially get your app rejected) or screenshot capture and overlay to hide and/or move the status bar