5 ms·

I agree. Almost anyone of these one size fits all approaches hits a wall sooner or later. Besides very basic applications, I would never make use of frameworks

I agree. Almost anyone of these one size fits all approaches hits a wall sooner or later. Besides very basic applications, I would never make use of frameworks like Flutter or React Native. Same goes for Windows Universal Apps. Great concepts, but not very feasible in reality for slightly complex apps with good UX.

makestuff 3y ago
Do you think it is worth the increased time to start out as a native app, or is it still worth rolling your MVP as flutter/reactive native?
- karmelapple 3y ago
  IMO, roll your MVP with something like React Native, although it all depends how important the user experience is for your end users. Snapchat built with some platform-independent UI toolkit would have felt kind of wrong, and the speed at which I've seen teenagers use it (this was years ago) shows that they would have been frustrated with anything that is slow-ish. I assume similar trends dominate for TikTok and Instagram today. So unless you're attracting a very hip, fast-moving, perhaps even young-person's market, you probably just want an app that basically works and is available to folks on whichever phone they use. React Native, Flutter, Xamarin / .NET MAUI will all get you there.
- mycall 3y ago
  This depends on the number of platforms you're trying to support. iOS, Android, mobile web, Windows and Linux? Flutter or Expo.
rnk 3y ago
I strongly disagree. This is just big companies artificially separating their market segments to argue against too large of a market, and preserve their enormous profits with their huge percentage take. The world would be much better off with multiple stores. It will take legal action by the eu, and it will be hard, these rich companies are very influential. In the us we have too much capture of federal politicans, I only hope the eu can push it.
- nextos 3y ago
  I hope multiple stores shake a bit the iPad ecosystem. It's a great device and, unlike in mobile, there's no competition. Android tablets are pretty bad. Google dropped the ball, although they seem to be coming back. iPads could be fantastic devices to program in, but they are quite crippled by limitations. Boutique software companies, such as Panic or Omni Group, plus other developers could really extend the ecosystem beyond content consumption and simple document creation tasks.
  - shagie 3y ago
    I believe that Google's ball drop with tablets has to do with that the phone manufacturers that Google partners with for Android are not as interested in tablets (likely using wifi) as they are with phones. Combine that with a lack of standardization and lack of focus for the tablet form factor... and that's what you've got. The iPad, on the other hand was the original "this is what we want". The iPad was the first thing that Apple was trying to make. > Work on the iPad itself actually traces back to 2004, when designer Jonathan Ive and others crafted a new tablet prototype. The product was originally supposed to ship before the iPhone, but the company came to decide the latter was more important, premiering it in 2007 using similar technologies. ( https://appleinsider.com/articles/18/04/03/a-brief-history-of-the-ipad-apples-once-and-future-tablet https://appleinsider.com/articles/18/04/03/a-brief-history-o... ) So from the very beginning with the iDevice, the idea of different form factors and sizes was part of how it was written rather than as a phone that grew bigger.
    - derefr 3y ago
      They've been trying to make the iPad since the Apple Newton. The tech to do it just wasn't there.
    - bhawks 3y ago
      The desktop OEMs lament their inability to differentiate their hardware offerings. I had always wondered why some of them didn't see the opportunity to enter the tablet space on Android as a path to differentiation. The only risk I would imagine would be the potential cannibalization of their laptop lines, but that really shouldn't stop them.
post-it 3y ago
I'm currently on a four-person team developing/maintaining a popular React Native app. Working with React Native is awful, but having two of us doing Android and two doing iOS would be worse.

makestuff 3y ago

Do you think it is worth the increased time to start out as a native app, or is it still worth rolling your MVP as flutter/reactive native?

karmelapple 3y ago
IMO, roll your MVP with something like React Native, although it all depends how important the user experience is for your end users. Snapchat built with some platform-independent UI toolkit would have felt kind of wrong, and the speed at which I've seen teenagers use it (this was years ago) shows that they would have been frustrated with anything that is slow-ish. I assume similar trends dominate for TikTok and Instagram today. So unless you're attracting a very hip, fast-moving, perhaps even young-person's market, you probably just want an app that basically works and is available to folks on whichever phone they use. React Native, Flutter, Xamarin / .NET MAUI will all get you there.
mycall 3y ago
This depends on the number of platforms you're trying to support. iOS, Android, mobile web, Windows and Linux? Flutter or Expo.

rnk 3y ago

I strongly disagree. This is just big companies artificially separating their market segments to argue against too large of a market, and preserve their enormous profits with their huge percentage take. The world would be much better off with multiple stores. It will take legal action by the eu, and it will be hard, these rich companies are very influential. In the us we have too much capture of federal politicans, I only hope the eu can push it.

nextos 3y ago
I hope multiple stores shake a bit the iPad ecosystem. It's a great device and, unlike in mobile, there's no competition. Android tablets are pretty bad. Google dropped the ball, although they seem to be coming back. iPads could be fantastic devices to program in, but they are quite crippled by limitations. Boutique software companies, such as Panic or Omni Group, plus other developers could really extend the ecosystem beyond content consumption and simple document creation tasks.
- shagie 3y ago
  I believe that Google's ball drop with tablets has to do with that the phone manufacturers that Google partners with for Android are not as interested in tablets (likely using wifi) as they are with phones. Combine that with a lack of standardization and lack of focus for the tablet form factor... and that's what you've got. The iPad, on the other hand was the original "this is what we want". The iPad was the first thing that Apple was trying to make. > Work on the iPad itself actually traces back to 2004, when designer Jonathan Ive and others crafted a new tablet prototype. The product was originally supposed to ship before the iPhone, but the company came to decide the latter was more important, premiering it in 2007 using similar technologies. ( https://appleinsider.com/articles/18/04/03/a-brief-history-of-the-ipad-apples-once-and-future-tablet https://appleinsider.com/articles/18/04/03/a-brief-history-o... ) So from the very beginning with the iDevice, the idea of different form factors and sizes was part of how it was written rather than as a phone that grew bigger.
  - derefr 3y ago
    They've been trying to make the iPad since the Apple Newton. The tech to do it just wasn't there.
  - bhawks 3y ago
    The desktop OEMs lament their inability to differentiate their hardware offerings. I had always wondered why some of them didn't see the opportunity to enter the tablet space on Android as a path to differentiation. The only risk I would imagine would be the potential cannibalization of their laptop lines, but that really shouldn't stop them.

post-it 3y ago

I'm currently on a four-person team developing/maintaining a popular React Native app. Working with React Native is awful, but having two of us doing Android and two doing iOS would be worse.