3 ms·

Something really telling for me here is the fact that there are multiple people here (representing multiple companies) who have solved this problem and there do

by atonse 4y ago

Something really telling for me here is the fact that there are multiple people here (representing multiple companies) who have solved this problem and there doesn't seem to be an open source solution for it, let alone a dominant one. It's clear that in general, we are all sick of writing a bunch of bespoke code and maintaining multiple platforms, and are seeking smart layers of abstractions over native widgets. It's a tale as old as time. What's curious is why there isn't a standard/de-facto standard (like JSON based one maybe?) for UI layouts that has emerged, with a React Native adapter for it. We are trying to solve this problem too with the same approach (the framework isn't the product, it's just because we don't want to spend too much time building custom Mobile components for our product). It's not like people haven't tried. Just Microsoft has probably a half dozen of these. MAUI, WPF, etc. Again, just curious that at least one format hasn't emerged for it.

api 4y ago
> What's curious is why there isn't a standard/de-facto standard (like JSON based one maybe?) for UI layouts that has emerged It hasn't emerged because nobody has done it. Nobody has done it because it's unbelievably hard and involves a lot of painful code of the sort that is not fun and therefore that people must be paid to write. Nobody has been paid to write it because nobody pays for dev tools and it's not in the best interest of any platform vendor to commoditize platforms.
- atonse 4y ago
  You could say all those things about react native or other frameworks. Like any reason why Airbnb can’t open source their solution? Seems battle tested. The thing is that many people HAVE solved this.
- alexhayes 4y ago
  Your correct this is hard, but I have to disagree that it involves painful code. Declarative UI in all 3 clients is a major enabler for doing this in a nice way. Some context - https://github.com/MobileNativeFoundation/discussions/discussions/47#discussioncomment-2673219 https://github.com/MobileNativeFoundation/discussions/discus... (Edit to add context)
jdmoreira 4y ago
I'm one of those people and in my opinion it would be hard to make a solution that fits all. The reason why it works for us is because we control the design system and we know the needs of our app and users. It works because it's somewhat bespoke to our use-cases. It simply is not possible to represent the realm of all possible native UIs within a common json schema. We can do it because don't need the realm of all possible UIs. We need a 20 different elements recombined and reused across all our screens. Which is also a strength because now we can leverage our limitations into delivering a consistent experience across our app.
- atonse 4y ago
  But that’s an argument about style. No reason why an opinionated version couldn’t come out I guess.
woojoo666 4y ago
If you have a React Native adapter on all platforms, why not just use React as your standard?
native_samples 4y ago
That was basically AWT and then SWT in the Java world. It can work for simple stuff. For anything more complex the underlying widgets are too different, you have to go with the lowest common denominator and the results just aren't good enough.

by atonse 4y ago

api 4y ago

> What's curious is why there isn't a standard/de-facto standard (like JSON based one maybe?) for UI layouts that has emerged It hasn't emerged because nobody has done it. Nobody has done it because it's unbelievably hard and involves a lot of painful code of the sort that is not fun and therefore that people must be paid to write. Nobody has been paid to write it because nobody pays for dev tools and it's not in the best interest of any platform vendor to commoditize platforms.

atonse 4y ago
You could say all those things about react native or other frameworks. Like any reason why Airbnb can’t open source their solution? Seems battle tested. The thing is that many people HAVE solved this.
alexhayes 4y ago
Your correct this is hard, but I have to disagree that it involves painful code. Declarative UI in all 3 clients is a major enabler for doing this in a nice way. Some context - https://github.com/MobileNativeFoundation/discussions/discussions/47#discussioncomment-2673219 https://github.com/MobileNativeFoundation/discussions/discus... (Edit to add context)

jdmoreira 4y ago

I'm one of those people and in my opinion it would be hard to make a solution that fits all. The reason why it works for us is because we control the design system and we know the needs of our app and users. It works because it's somewhat bespoke to our use-cases. It simply is not possible to represent the realm of all possible native UIs within a common json schema. We can do it because don't need the realm of all possible UIs. We need a 20 different elements recombined and reused across all our screens. Which is also a strength because now we can leverage our limitations into delivering a consistent experience across our app.

atonse 4y ago
But that’s an argument about style. No reason why an opinionated version couldn’t come out I guess.

woojoo666 4y ago

If you have a React Native adapter on all platforms, why not just use React as your standard?

native_samples 4y ago

That was basically AWT and then SWT in the Java world. It can work for simple stuff. For anything more complex the underlying widgets are too different, you have to go with the lowest common denominator and the results just aren't good enough.