XD export feature to xCode
Add xCode export to the list of functions... great for informative apps
Can you tell us more about how you’d like this to work? Do you want XD to export image assets and insert them directly into the correct folders/filenames in an existing Xcode project? Or do you want XD to generate Objective-C / Swift code to create a brand new Xcode project?
Please! XD to generate Objective-C / Swift/XML code to create a brand new Xcode project. How close are we to this being possible? Thank you so much!
Designing a (IOS) prototype app with XD works perfect.
Coding in Swift through X-Code works perfect too :)
Linking the prototype from XD with the code from X-Code and launching the actual product in the app store would mean to melt the best of those two worlds!?
What do you guys think?
William Davis commented
Either way, but I like the concept of developing the UI first in XD then creating the Xcode project using the imported UI
Evan Alexander commented
we really need for XD it a pain to export to xcode
It could be a « save as » feature to create a xcode project
As a UX Designer and Swift developer, I would absolutely love the ability to export an XD project to a new Xcode swift project. Properly constrained assets in either Swift code or Storyboard would be wonderful. :)
Boyo Darwin commented
I would like to export my Adobe XD project to a new XCode project. This should be quite simple. XCode is based on storyboards, which is pretty much what XD is. This could work by importing the assets and creating the default XCode project files, and inserting the design into the storyboard. For example, I just finished designing a simple informative app. I want to put this into XCode, but it is much simpler to create prototypes on XD than to actually put it into XCode. If you could add a function that would create a boilerplate, or "template", that would be fantastic.
XD to generate Objective-C / Swift/XML code to create a brand new Xcode project
It would be incredible to get an output .xib file using auto-layout from an XD art board.
I know there would be an extra step of opening, then copying the xib into Main.storyboard but the time savings would easily make up for that without having to hack into Main.storyboard (though, maybe that's not a horrible idea?)
Yes please I need this
I would like XD for laying out everything, and then exported to Swift view controllers for each pages. That would be super nice. Laying out in XD is much easier than Xcode.
Jo Jacobs commented
Hi there, I really can recommend http://www.psd2xcode.de from j-apps. Even if it is only in Version 1.2 (Cause we are a 2 men developer team only) it works fine with Photoshop and does generate the storyboard and all assets for your App, including all image sizes needed.
maybe Adobe is interested to have a cooperation do the same with XD?
Best regards, Jo Jacobs
I want a WORKING model! So that means exporting it into X-code, ready to go as an app (provided we've met all the correct Apple design criteria).
In Muse, I am SO limited on Java/buttons/animations that I have to go out to Animate or Ps or my worst nightmare Ai and do the interactions, then import those BACK into the "design" in Indesign, THEN put that on XD...it's just too many steps to set up.
I get using one program to design pretty elements, then importing those into my UI design program (which honestly id is way better than muse for this, at least functionality wise). But from there, I want my UI design to be functional and ready to export to Xcode (Swift). I really had hoped XD would do this, but honestly why would I use XD instead of just keeping it in indesign?
My dream? A Dreamweaver for Apps. Where I put everything in in html/css/java code or real-view (my choice to code it or use graphics screen--bc Adobe preset buttons never do what I want and they don't animate well BUT I don't want to have to write code when I could just drop it in from library).
I create real, beautiful, functional apps, and I don't see why Adobe doesn't make it so I can create the gorgeousness AND functionality in Adobe and easily export it to Apple Swift!! It really makes me want to just ditch Adobe except photoshop and code the whole thing in Swift instead...but I really don't want to do it that way because--UGH coding makes me cross eyed and its ugly.
Alexander Mallinckrodt commented
I want XD to export image assets and insert them directly into the correct folders/filenames in an existing Xcode project. Or XD to generate Objective-C / Swift code to create a brand new Xcode project, i'm not entirely sure which is better, it's up to you.
Adam t commented
We need export assets directly to FTP SERVER , just like Adobe Muse , is it difficult to understand ? We need working page , no prototype !
When direct app creation from XD will be implemented?
As a designer and hobbyist coder I can tell you that while coding in swift is easily learned there are no truly great resources that I've found for working well with Xcodes interface builder.
Being able to design in xd and import to Xcode having my entire storyboard laid out (text as UIlabel etc...) would be hugely valuable to me.
Graphic assets should be exported in SVG format, so that they can be included in the app project and displayed using one of the many SVG native libraries for iOS, Android, etc. The xcode or android project must include the library and display the svg assets as separate elements, so that they can be made interactive by the coder.
might look at sympli.io, their Android Studio and Xcode plugins
It could be a new XCode project so to not mess up with current one, where text would be converted to UILabel, and if this label is in Navigation bar group and it's positioned in a centre - it could be recognized as NavigationBar Title with all it's properties.
Instead of transferring navigation bar background as an image –> to rebuild it using native tools.
If it's vector graphic shape –> to store it in assets as pdf.
So it could be a step further. So developers will have some base point from which to start. Colors, fonts, sizes. Of course it should be some additional work with auto layout features, but it will be better to refer an example from the native iOS environment, instead of tinkering around in different prototyping tools, and design descriptions.
In this sort of way the gap between designer and developer could be vastly narrowed.