3 ms·
After you get past the initial pain, it's native Java & Swift. Implementing something twice seems like a bad idea, but after fiddling with "cross-platform wanna
by s1k3s 5y ago
After you get past the initial pain, it's native Java & Swift. Implementing something twice seems like a bad idea, but after fiddling with "cross-platform wannabe" solutions I can safely say that native is the way to go. I can do it for you if it's as easy as you make it feel, if you want to.
- jonplackett 5y agoI would agree with this if Java / android SDK was as nice as swift.
- s1k3s 5y agoYeah I agree, what they did with Swift / the iOS library is an absolute masterpiece, but I feel like conceptually they're very much the same and once you've got the hangs of one, you'd easily switch to another, at least for a project as simple as OP says it is.
- ekola 5y agoKotlin and compose UI are way better
- GoldenMonkey 5y agoKotlin for native android is great!
- GoldenMonkey 5y agoKotlin of course for native android. Java is dead for android development… no point in using it with new apps.
- pwfcurry 5y agoI've worked on a production app written in react native for 3 years - if the use case is as simple as you say, it should be absolutely fine. It can become an issue when interacting with eg camera or Bluetooth, bur that's likely to be the case anyway. Expo is pretty good. Anecdotal of course, but there is a reason react native / expo exist and are as popular as they are.