14 comments

  • Saffad KhanSaffad Khan, almost 4 years ago (edited almost 4 years ago )

    Nice tutorial, easy to follow.

    My issue with this is that it's not a better solution for most common needs. If the goal is to communicate a flow, have it on a real device and share then Invision, Flinto or Marvel does all of that but better. They have more transitions like push and it's faster. It sounds cool to use xcode, but at that point you might as well use what it's for and write some code.

    4 points
    • Matt ScorteMatt Scorte, almost 4 years ago

      Yes, this was my question exactly? Would the only benefit be that it is free? Also, which of the 3 prototype tools do you prefer?

      0 points
      • Saffad KhanSaffad Khan, almost 4 years ago

        Depends on your goals. When i want to communicate a flow I use Flinto for mac. You can also create your own transitions which is a bonus.

        0 points
      • Mike Godlewski, almost 4 years ago

        Also, this solution wouldn't be free since you pay $99.00 per year for Apple Developer access. Invision is my go-to between those three.

        0 points
    • Rafael Conde, almost 4 years ago

      That's a very good point, and you're right from what we can see in this video – but there's potencial for, and it can be covered in future videos, to start using real iOS components like tab bars, navigation bars, peak and pop, so on and so forth.

      So we could in theory start having a very real behaviours from a real iOS app.

      With that said, I'm a huge fan of Framer, Marvel and all of the prototyping tools, just thought it could be interesting to explore Xcode as an alternative.

      0 points
  • Sagi ShrieberSagi Shrieber, almost 4 years ago

    Great tutorial Rafael! I really want to get more into Xcode for prototyping and this certainly helps!

    2 points
  • Rory Smyth, almost 4 years ago (edited almost 4 years ago )

    Where's the value in this?

    2 points
    • Rafael Conde, almost 4 years ago

      Like Invision or Marvel, creating an interactive flow of your mockups – ready to test and install on a real device?

      Am I missing something?

      5 points
      • Rory Smyth, almost 4 years ago (edited almost 4 years ago )

        I was more talking about the effort vs output. It seems like a lot of work compared to using one of the other prototyping tools. For something as simple as a screen transition. Interesting regardless.

        2 points
    • Miguel CampiãoMiguel Campião, almost 4 years ago

      Self-explanatory on the title.

      1 point
    • Sagi ShrieberSagi Shrieber, almost 4 years ago

      wow, these kind of comments are the reason I'm reading DN :) Just gotta love the community here.

      2 points
  • Joshua MillerJoshua Miller, almost 4 years ago

    Similar concept to the design code chapter 2

    Very nice for a "native-esque" build to deploy and show stakeholders/dev teams.

    Also this is a nice way to learn the interface if you're a designer wanting to tinker with Objective-C or Swift.

    1 point
  • Carl Yung, almost 4 years ago

    "You need to install Adobe Flash Player to play this video." Really, in 2016?

    0 points
    • Rafael Conde, almost 4 years ago (edited almost 4 years ago )

      That's weird, I don't even have Flash installed an it plays fine (oh and the video is being handled by Vimeo).

      0 points