As you&#x27;ve worked in games, perhaps the designers you&#x27;ve worked with are more adept than average at taking up new tools...? At least that is my experience. Game artists often have experience with all sorts of in-house tools with UIs of highly varying logic and consistency, whereas most &quot;traditional&quot; designers have used Adobe tools and nothing else.<p>It seems to me that the success of Sketch lies in how little it diverges from the Adobe formula. Sketch doesn&#x27;t really add any new significant mental model: it adopts Illustrator&#x27;s terminology (such as artboards) and some of Photoshop&#x27;s bitmap capabilities, and cleans up the three decades of cruft that obstruct the Illustrator and Photoshop interfaces. That has clearly been a good recipe for something that&#x27;s easy to pick up for designers.<p>The UI layout tools in Xcode and Android Studio are not like that. The learning curve is very steep. Interface Builder is a tangled mess of quirky NeXT legacy and complex new concepts like auto-layout constraints. Android Studio&#x27;s UI editor is worse because it&#x27;s &quot;property editor hell&quot; -- editing layouts by twiddling Android&#x27;s endless and confusingly named properties will drive designers mad. (I used to think that Microsoft&#x27;s Visual Basic was the epitome of this type of tool, but Android is much worse.)<p>I&#x27;ve worked on a tool called Neonto Studio that tries to provide a designer-friendly cross-platform mobile UI solution:<p><a href="http:&#x2F;&#x2F;neonto.com" rel="nofollow">http:&#x2F;&#x2F;neonto.com</a><p>It generates native code for both iOS and Android, there&#x27;s no framework.<p>It has been really difficult to figure out a layout model that is both understandable to designers with Adobe&#x2F;Sketch background _and_ can translate reasonably well to iOS and Android classes! Our current effort is pretty good, but it definitely has room for improvement.<p>Still, I would suggest that Neonto Studio is a much gentler way to introduce mobile UIs to a traditional designer than throwing them into the deep end of Interface Builder or Android Studio :)