I'm a designer who's tinkered with some code. I've recently learned @CreatewithPlay, which was a relatively smooth transition if you know Webflow and Figma at a decent level. Learning Play was a stepping stone to learning Swift. Using Play before learning Swift was almost like a prep course for it. This video validates that so much. Great partnership Play! Hell of an ad.
3:02 agreed that wouldn’t likely expect a designer to be reading SwiftUI docs… but wow, glad it’s there! As a very beginner hobbyist that dabbles in SwiftUI at times, this is a fantastic learning “cookbook” if you will.
Great video. This tool can finally change my working method with the designer. I used to see the code from Figma, but this is game-changing. Can u make some other videos with this tool for making a complete app, just from a UI perspective?
So Sean, question on this video. I can see the value of a team targeting an MVP for an app with iOS first as their main iteration. This product brings powerful features for UI/UX to move the ball forward quickly. But, what if you're a small Indy team where it's just 3 people or just a single developer? I've struggled between Play, Figma, and just pencil and paper as to the best approach. What would you recommend in "most cases"? Thoughts?
My opinion... if you don't have a designer and it's just 1 developer that's in charge of design and development, then I do a quick pencil/paper sketch and hop right into SwiftUI (as the developer). I think Play is a no-brainer if you have someone full-time on design that can work through a LOT of design issues, and then the developer builds it.
This is good if you are only targeting for iOS right? In most of my jobs they want to output to both Android and iOS and I would imagine the dev from Android would have to recreate a lot of the Swift interaction/animation or find an alternative way to present it?
Just tried it, pretty unimpressed. It just lost 30 minutes of work because I clicked on a component i made and it reset back to its default state. Clicking undo didn't do anything. That was just one of many bugs, and I didn't find the interface at all intuitive. No thanks!
How would this work where you have an app that runs both on iOS and Android? Would the designer have to use a different "UI" for Android or is this only for iOS only apps?
I am following play from their launch and still don't understand why it's undervalued. I have a couple of observations about their marketing strategy. they are just posting feature videos (most of them 3-5 min) But it's a new product, I think they should post a 2-3 hours tutorial to create an entire app from scratch to cover whole software's abilities.
This doesn't help if you support Android and iOS. At the very least, Play needs to export a spec sheet with the name of the Material Design's components and maybe a video of the interaction.
It feels like it fixes a problem that doesn't exist. Designers don't need to think "SwiftUI", they need to think about "User experience". It's the developer's job to implement it, and it doesn't matter what tech stack they use and how they implement it
doesn't really work like that. Our designer can give me anything he wants, if I got to my manager and tell him it will take me 2 days to build this fancy looking screen with custom tabbar that amazingly bends and flashers when I tap on it, he will make the designer redo it... And there will be a problem if this pattern keeps repeating.
Well said, @kironet. In a "perfect world" the designer designs whatever they want and the developer builds it. But in real life you have limited time and resources. If you're spending all the developer's time building fancy custom UI elements (reinventing the wheel), then you are spending expensive developer resources on the wrong thing. Of course, there are exceptions. If a huge part of your app's brand is to have whimsical, fancy designs, then that's a different story. But I'd argue that only applies to a very small subset of apps.
@@kironet I'm not talking about going against HIG or using some crazy custom animations. All I'm saying is a designer can use Apple's components library in Figma and make a design. And if the components are created right, you can switch them on and off with one click as well. They don't need to worry about SwiftUI
@@numb980a figma prototype gets nowhere near the fidelity that’s on show here. This opens up a whole new world for startups looking to quickly user test and gain backing from investors without coding a whole app.
A figma prototype gets nowhere near the fidelity that is on offer here. The amount of time and money this saves in creating a hyper realistic take an end state app to then user test with or even gain funding from investors is a game changer!
A typical developer view. F* custom design. Just give me backed in components of Swift UI. Don't misunderstand me at all. There is a place and time to think in this way. But man designers can learn about Swift UI capabilities and create different experiences.
I think the point is that Swift UI makes it really hard to design custom UI (much harder than UIKit), which makes a tool like this more useful. It would be interesting to hear how Play supports custom UI if they do.
@@alexthurston9940 Great question! You can design anything in Play similar to how you would design in Figma. We use V,H,Z Stacks vs Figma's Auto Layout and we work to take whatever you design and generate SwiftUI code that can be used in Xcode to lay out those same views.
