3 ms·

I’ve come to the same conclusion. I began to build a very simple app about a month ago and as a Web Dev figured React Native would be the best tool. Having comp

by scop 3y ago

I’ve come to the same conclusion. I began to build a very simple app about a month ago and as a Web Dev figured React Native would be the best tool. Having completed about 60% of the app, I’m going to trash the whole thing and restart with Swift/Kotlin. I’ve encountered too many “quirks” that end up burning a huge amount of time for what should be an inconsequential component.

ramones13 3y ago
You might want to check out CapacitorJS - https://capacitorjs.com/ https://capacitorjs.com/ It’s more web than RN and depending on what you’re doing might not feel as native, but it’s pretty easy to make a solid app with it.
samtheprogram 3y ago
Using Swift UI, or UIKit, has its own quirks. And then you need to shift mental gears with entirely different UI component paradigms. I find most people making this argument haven't worked full time with one or the other. If you're a larger company who can afford two teams/groups, or if you are working on something lower level like OpenGL or ML, it makes sense. Having done both for multiple years, I can't understand when people think it would be faster to build separate apps. It's not even remotely close. You're swapping out doing bug fixes, platform specifics like push notifications, the occasional separate UI implementation, and distribution twice with doing _everything_ twice.
mpweiher 3y ago
For some bizarre reason I haven't figured out yet, it seems like the "cross platform" choice is always the worst one. So when people talk about cross-platform on the Mac, for example, it's always some JavaScript abomination, or Java, or Delphi (yes, seriously), or Go. How about going the other direction and getting Cocoa running somewhere else? GNUstep, Cocotron etc. Gosh, that would actually make sense, can't have that. Literally. In fact, one company did. Apportable. Google bought them and buried the tech. Hmm
- lockhouse 3y ago
  It’s not perfect by any means, but SwiftUI is the most productive development stack I’ve ever used for GUIs. There’s definitely a huge learning curve and some rough edges, but the speed with which I can write a polished UI in it is staggering.

by scop 3y ago

ramones13 3y ago

You might want to check out CapacitorJS - https://capacitorjs.com/ https://capacitorjs.com/ It’s more web than RN and depending on what you’re doing might not feel as native, but it’s pretty easy to make a solid app with it.

samtheprogram 3y ago

Using Swift UI, or UIKit, has its own quirks. And then you need to shift mental gears with entirely different UI component paradigms. I find most people making this argument haven't worked full time with one or the other. If you're a larger company who can afford two teams/groups, or if you are working on something lower level like OpenGL or ML, it makes sense. Having done both for multiple years, I can't understand when people think it would be faster to build separate apps. It's not even remotely close. You're swapping out doing bug fixes, platform specifics like push notifications, the occasional separate UI implementation, and distribution twice with doing _everything_ twice.

mpweiher 3y ago

For some bizarre reason I haven't figured out yet, it seems like the "cross platform" choice is always the worst one. So when people talk about cross-platform on the Mac, for example, it's always some JavaScript abomination, or Java, or Delphi (yes, seriously), or Go. How about going the other direction and getting Cocoa running somewhere else? GNUstep, Cocotron etc. Gosh, that would actually make sense, can't have that. Literally. In fact, one company did. Apportable. Google bought them and buried the tech. Hmm

lockhouse 3y ago
It’s not perfect by any means, but SwiftUI is the most productive development stack I’ve ever used for GUIs. There’s definitely a huge learning curve and some rough edges, but the speed with which I can write a polished UI in it is staggering.