4 ms·

It's one of the reasons I prefer Storyboards over coded views in iOS development. The immediate feedback in the designer instead of compile / reload. They even

by dep_b 11y ago

It's one of the reasons I prefer Storyboards over coded views in iOS development. The immediate feedback in the designer instead of compile / reload. They even got better with live views. Having the behavior simulated for different data sets would be the icing on the cake for me. This idea is so great it makes me wonder why it didn't exist yet (but perhaps there's something very similar out there already?)

stevenhuang 11y ago
I developed in Android first, then iOS, and I don't like storyboards (git merge conflicts, clunky drag/drop outlets, and more). I also found the XCode ide to be pretty terrible compared to Android Studio.
- hellofunk 11y ago
  Storyboards take a while to set in, but once they do, you'll see why so many people save so much time with them.
  - thewarrior 11y ago
    I have about 3 years of iOS experience and I have a love hate relationship with storyboards. I think the introduction of auto-layout has made it them more powerful , but also a bit confusing. Apple really needs to work on the UX in interface builder. I should ideally be able to see most of the constraints at a single glance rather than clicking on each every view to find out how it relates to the views around it. I can create UIs reasonably fast now , after mastering all the tricks and UI shortcuts. However as your parent mentioned , it is a fact that Android developers are able to create UIs faster. I know this since our team works on the same features on both platforms. It used to be that Android used to really suck , but for simple standard UIs , mocking up something is much faster now on Android. And their layout system while not as powerful as Autolayout is enough most of the time and easier to grok. The only thing they still struggle with are animations and device / OS fragmentation.
modarts 11y ago
The idea has been around in the frontend community for years in the form of UI harness and hundreds of other react based projects like this one that do effectively the same thing.

by dep_b 11y ago

stevenhuang 11y ago

I developed in Android first, then iOS, and I don't like storyboards (git merge conflicts, clunky drag/drop outlets, and more). I also found the XCode ide to be pretty terrible compared to Android Studio.

hellofunk 11y ago
Storyboards take a while to set in, but once they do, you'll see why so many people save so much time with them.
- thewarrior 11y ago
  I have about 3 years of iOS experience and I have a love hate relationship with storyboards. I think the introduction of auto-layout has made it them more powerful , but also a bit confusing. Apple really needs to work on the UX in interface builder. I should ideally be able to see most of the constraints at a single glance rather than clicking on each every view to find out how it relates to the views around it. I can create UIs reasonably fast now , after mastering all the tricks and UI shortcuts. However as your parent mentioned , it is a fact that Android developers are able to create UIs faster. I know this since our team works on the same features on both platforms. It used to be that Android used to really suck , but for simple standard UIs , mocking up something is much faster now on Android. And their layout system while not as powerful as Autolayout is enough most of the time and easier to grok. The only thing they still struggle with are animations and device / OS fragmentation.

modarts 11y ago

The idea has been around in the frontend community for years in the form of UI harness and hundreds of other react based projects like this one that do effectively the same thing.