Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Svelte Native

svelte-native.technology

Post reply on HN
Print view View original

51–60 of 93 posts

Re: Svelte Native

#51

Post by rizky05 »

conradfr wrote: post #46
imgabe wrote: post #36

I’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.

People should just use Ionic & Capacitor. You can still use your React knowledge with it.

[dead]

Re: Svelte Native

#52

Post by whizzter »

scosman wrote: post #16
papa_bear wrote: post #15

My company tried using this a few years ago to build a cross platform app (and hopefully share a lot of code with our svelte web interface). We made a lot of progress in 3-4 months of trying, but we ended up running into too many odd bugs and edge cases that were difficult to debug. We eventually switched to Flutter for the mobile codebase. No doubt this and nativescript have improved since then, but from my early im…

This is the story I’ve heard about almost every react native project. Get to proof of concept 10x faster. Spend 10x more time in the weeds on weird bugs.

Did they have JS _AND_ React experience beforehand? Or did they just pick RN because it was the cool thing on the block?

I foundered on my first attempt at an React app (side project) coming from a C,C++,Java and non-React JS background, but the second one(professionally) after I've had exposure to some React got released and an fork of it is still in use today. And the company I work with has 2-5 other apps out for customers using RN/Expo (thanks to the positive experience I had).

We're also strict about using TypeScript though so we're not chasing basic type bugs (since debugging is a tad weaker with RN/Expo even if it's usable if shit the fan only occasionally) and we have plenty of React experience outside of it, biggest "quirks" are often RN/Expo upgrades if we haven't maintained things in a while (the oldest app used a relatively early version of Expo though) or platform specific notification crap (that I've heard is painful regardless of Expo/RN).

Re: Svelte Native

#53

Post by meowtimemania »

fakedang wrote: post #47
rareitem wrote: post #44

Earlier quoted context omitted.

I agree with you. RN still sucks on some aspects, but it's quite an amazing technology and I'm grateful it exists.

Nah, among cross-platform, RN has stagnated while Flutter has sped past. 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.

I had bad experiences with it 7 years ago, but really good experiences with it recently. If you stick to native modules managed by expo you'll be in a great place! You can run into dependency hell if you use a random react-native npm module that was last updated 5 years ago.

Re: Svelte Native

#54

Post by jamil7 »

wharvle wrote: post #42
imgabe wrote: post #36

I’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…

Although I haven't used it, Jetpack Compose exists now, so that and SwiftUI are pretty similar. On a previous project I was contracting on, the CTO managed to bash out a basic Android version of the iOS app I was working on without any Kotlin experience by going through the SwiftUI views one by one and implementing them in Jetpack Compose.

Re: Svelte Native

#55

Post by lakomen »

jd3 wrote: post #43
imgabe wrote: post #36

I’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.

We recently threw out our React Native app and have gone all in on PWAs.

TWA as well? Because I find, the app stores are good for discovery.

Re: Svelte Native

#56

Post by mixmastamyk »

pjmlp wrote: post #19
ultra_nick wrote: post #17

Earlier quoted context omitted.

SDKs for 4+ platforms is added tooling...

It is when it represents debugging the same code 4+ times. That is the fallacy of all these leaky abstractions, the need to actually know the native APIs from each platform doesn't go away. Someone needs to take care of integration problems.

Yes. Want to ship on N platforms, with the cross platform lib now you need to know N+1 platforms.

Re: Svelte Native

#57

Post by dangerlibrary »

sacrosanct wrote: post #26
woahitsraj wrote: post #23

While I'm a huge Svelte fan, this project hasn't really gotten very much care and attention over the last few years. Which is honestly fine. React and React Native I think do a much better job of filling the niche of people who want to build native apps with web tech. That being said, I think with the progress that Safari has made in implementing PWA support, the increased hostility of Apple toward native developers,…

> The only major hurdle to this is Apple continuing to treat web apps as second class citizens on iOS If you add a site to iOS' homescreen it automatically becomes a PWA. The best example I found of a site fully leveraging this feature is Cryptee[0]. They talk about the PWA thing here: https://crypt.ee/download [0] https://crypt.ee/

Fastmail does this too, and it works extremely well.

Re: Svelte Native

#58

Post by factormeta »

conradfr wrote: post #46
imgabe wrote: post #36

I’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.

People should just use Ionic & Capacitor. You can still use your React knowledge with it.

Capcitor with solid or marko would be better, more lightweight.

Re: Svelte Native

#59

Post by ex3ndr »

solarkraft wrote: post #14

Why does NativeScript seem so much worse than React Native?

Because they run JS on main thread while react native tries to minimise it at all costs (only keeping rendering and animations, but not layouts for example).

Re: Svelte Native

#60

Post by ex3ndr »

imgabe wrote: post #36

I’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.

This is a very weird thing to say when expo is literally one line installation and it does not require you anything to be installed (even XCode) on machine for most projects. It is literally 10x times easier than just writing in Swift.
Post reply on HN