Powered by NativeScript Hell no. It’s better to stick with RN if you want cross platform. Writing an app in Kotlin and Swift is easier compared to this contraption.
Svelte Native
41–50 of 93 posts
Re: Svelte Native
#42I’ve done a couple React Native apps and never again. They’re fine at first but if you let one sit for a few months there is a combinatorial explosion of complexity among shifting incompatibilities of different versions of javascript libraries, the framework, android/iOS versions, build systems, etc. it becomes a nightmare. I’d much rather just learn Kotlin/Swift and have only one ecosystem to maintain.
But that was like 5 years ago so maybe it's gotten better.
Re: Svelte Native
#43I’ve done a couple React Native apps and never again. They’re fine at first but if you let one sit for a few months there is a combinatorial explosion of complexity among shifting incompatibilities of different versions of javascript libraries, the framework, android/iOS versions, build systems, etc. it becomes a nightmare. I’d much rather just learn Kotlin/Swift and have only one ecosystem to maintain.
Re: Svelte Native
#44I’ve done a couple React Native apps and never again. They’re fine at first but if you let one sit for a few months there is a combinatorial explosion of complexity among shifting incompatibilities of different versions of javascript libraries, the framework, android/iOS versions, build systems, etc. it becomes a nightmare. I’d much rather just learn Kotlin/Swift and have only one ecosystem to maintain.
At the time I used it, it was almost worth it just to use RN for Android even if you did iOS in Swift, just because styling on Android was so hellish ("There must be some non-crazy way to set a default typeface for my app. Right?" LOL wrong; "setting this color on this Material input field must be easy" LOL nope, welcome to Java metaprogramming just to set a goddamn color), the documentation-suggested way to structur…
Re: Svelte Native
#45Whatever the merits of this project -- and it does seem to be useful -- they should be a little clearer about the fact that it's not actually part of the "official" svelte framework. I'm sure they consider it a tribute but it fees a little deceptive that they're cloning the svelte docs look and feel without any kind of "who we are" statement.
Re: Svelte Native
#46I’ve done a couple React Native apps and never again. They’re fine at first but if you let one sit for a few months there is a combinatorial explosion of complexity among shifting incompatibilities of different versions of javascript libraries, the framework, android/iOS versions, build systems, etc. it becomes a nightmare. I’d much rather just learn Kotlin/Swift and have only one ecosystem to maintain.
You can still use your React knowledge with it.
Re: Svelte Native
#47Earlier quoted context omitted.
At the time I used it, it was almost worth it just to use RN for Android even if you did iOS in Swift, just because styling on Android was so hellish ("There must be some non-crazy way to set a default typeface for my app. Right?" LOL wrong; "setting this color on this Material input field must be easy" LOL nope, welcome to Java metaprogramming just to set a goddamn color), the documentation-suggested way to structur…
I agree with you. RN still sucks on some aspects, but it's quite an amazing technology and I'm grateful it exists.
The key issue I see these days is that it's just not worth it to build a mobile app these days unless your payment flow happens outside of the app.
Re: Svelte Native
#48Powered by NativeScript Hell no. It’s better to stick with RN if you want cross platform. Writing an app in Kotlin and Swift is easier compared to this contraption.
[flagged]
Re: Svelte Native
#49Earlier quoted context omitted.
The whole add to home screen process is needlessly convoluted. It would be nice if there was something similar to Smart Banners for PWAs: https://developer.apple.com/documentation/webkit/promoting_a...
You just click "Share -> Add To Home Screen." I understand that that's technically more clicks than a smart banner but hardly "convoluted"
It's hard to make this point without linking to a screenshot, but the share menu is incredibly bloated. To get to the add to home screen button a user has to know it's in the share menu (which is just an unlabeled icon), and then scroll past the following menu items:
- An options button (which leads to another menu)
- Air Drop
- Share via text message (with several different contacts listed individually to share with)
- Copy
- Add to Reading List
- Add Bookmark
- Add to Favorites
- Add to Quick Note
- Find on Page