Is React Native the way to go for building native iOS and Android Mobile Apps? What have you used or learned from your company?https://www.cirtru.com

fannysurjana's profile thumbnail
Depends on who you ask :) Native developers will say native is the way to go (at the expense of time). I asked an Android dev one time about React Native and he scowled. I'd imagine React Native's coverage wouldn't be as rich as native app.For MVP building, any tool that you can use to get your product out to your customers ASAP is a good tool. I'd argue React Native is perfect for this purpose.
krimy's profile thumbnail
jennykwan's profile thumbnail
The question is always pros and cons.If you need features custom specific to the hardware, like accelerometer, or brightness meter, etc., then you have to go native.If you need to do anything performance critical, like rendering of video or audio (like gaming), or even visualization of large amounts of data, native is PROBABLY necessary.I looked at your site. These seem doubtful, so you can probably use React Native.The pros of React Native:- Portable code-base - you can use the same code for web as well as mobile native - helps with UX consistency- Larger pool of developers- Less technical debt == more agile as the product changes (this is only true if the engineers actually architect functionally)The pros of mobile native:- Easier to customize UX for properties of hardware (like screen dimensions)- More mature libraries for complicated features (data controls, etc.)- Less likely to rathole on performance problemsGiven what I *think* your product is, I recommend React Native.When making these choices, the best input comes from people who 1) go through this pro/con process with business factors in mind, and 2) have actually built things using all of the options on the table.I've built React apps, toy stuff in React Native, and toy stuff in Android with Java. Not much all around (I'm data, back-end, and server systems focused). I only gather facts from people much stronger in one tool than another, but do not take their decision making into account - they are biased by being much more familiar with one thing than another.
krimy's profile thumbnail
Thanks @jennykwan
Nastya's profile thumbnail
Hi there! If you are just prototyping and not planing to build an animation heavy app, go for react native. I build and released my app for iOS and Android using react native in under 2 weeks https://wod.voopty.com/ the app is just a webview which can handle push notifications, but it is more then enough for what I’m doing now. Side benefit - I do not need to go through approval process every time when I’m changing ui. But of course my approach would not work is the app would have been a game or required tight integration with a device
Nastya's profile thumbnail
Now I’m working on Apple Watch version of the app where I need to get access to HealthKit And be little more cautious about memory usage. in this case my only viable option is to native app