Strange that they didn't mention hiring as a reason, it's maybe even the main one. React is for the frontend what PHP was for backends in the 2000s, that's what most frontend devs know. Svelte would be a better fitting comparison to Rails in 2004.
Building all of our new mobile apps using React Native
91–100 of 588 posts
Re: Building all of our new mobile apps using React Native
#92Is there a reason that the web is not a target of react native? It seems somewhat insane to have a cross platform approach and leave out the biggest platform of all, the web. Or - looking at it the other way round - what approaches are there to take a working pwa website and turn it into an app? What advantages over such an approach can react native bring to the table?
The Ionic team recently released React support so you can build a PWA using React and target iOS, Android, web, and electron. Uses Capacitor under the hood for full native access. It’s been getting a lot of usage since the release: https://ionicframework.com/blog/announcing-ionic-react/
Also you can use Capacitor with any PWA-style web application without using any of the rest of the Ionic Framework. https://capacitor.ionicframework.com/
It's currently the best maintained successor to PhoneGap/Cordova.
Re: Building all of our new mobile apps using React Native
#93Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
Running a UI within a virtual machine is the stupidest idea ever.
Re: Building all of our new mobile apps using React Native
#94Earlier quoted context omitted.
The sites I build at work have proper push notifications. This problem has already been solved.
How did you solve the lack of push notifications on iOS?
For iOS, can't you just wrap your web application in a thin native app layer that provides the push functionality?
Re: Building all of our new mobile apps using React Native
#95Earlier quoted context omitted.
Look at your most used apps - none of them are "responsive pages". That should tell you something. Folks who have tried responsive pages haven't done that well. I am curious - what is the most popular responsive webpage on iphone would people say? I'd like to check out the current leader in this space.
I use Facebook's as I don't want Facebook's grubby hands using private APIs on my phone to get every bit of data they can. At least the browser limits them.
Plus the facebook app eats battery life. IME my phone battery lasts all day unless I install facebook: then it lasts a few hours.
Re: Building all of our new mobile apps using React Native
#96Curious to hear more about their deep dive into Native, Flutter and React Native as possible technology choices. Hopefully, React Native is not a nosedive ;)
Flutter and React-Native are different directions, I think. For higly customized UIs (think Ableton Live, Photoshop, Excel, etc.), I'd say use Flutter, because of the non-native rendering, it will look the same everywhere. Otherwise use React-Native.
Exactly this. They are very different systems.
Flutter renders onto a "canvas" and has a completely custom implementation of "native-like" views for each platform. They need to reimplement everything about platform views from scratch.
React Native lets the native OS render actual native views, but lays them out and controls their properties using Javascript. You get the native behaviours "for free", but you do sometimes end up in the lowest common denominator position.
Re: Building all of our new mobile apps using React Native
#97Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
I feel quite the opposite, most of the phone apps will likely to be thick client variants of the web apps, given that the hosts have so much power and storage available. Privacy concerns are gonna force this model where almost every activity having minimal network overhead. We are going back to the desktop app era, is what I feel.
> We are going back to the desktop app era, is what I feel.
Can't wait, to be honest. This era of everything as a service is great for developer convenience but is incredibly user-hostile in that it enables and encourages surveillance capitalism and the erosion of privacy.
Re: Building all of our new mobile apps using React Native
#98Earlier quoted context omitted.
It can't be overstated how many apps are absolutely dependent on working push notifications (all chat for example) and can't be replicated as websites. And that's not yet implemented for iOS so we're all at Apple's mercy until it is, which may never be.
I can’t stand push notifications, I disable them all except for a couple (like signal). They are usually only part of the app to manipulate you into using it constantly
What's your point? Do you think you represent most people? Can you not just turn it off?
Notifications have fine tuned controls on both iOS and Android with schedule Do Not Disturb features and varying levels of priority (iOS has 3 tiers). Plus per-app controls to disable them from annoying apps, which in newer versions of iOS prompt you before they turn on, making them opt-in.
It's essential for communication apps (texting, email) and useful for breaking news or a simple highlight of big news on WSJ/NYT on your activity feed, so you don't need to open either app to stay on top of big events if you're a news junkie like me.
I'd personally go as far as saying push-notifications + the activity feed is very underrated feature of smart phones and has become a core part of people's day-to-day lives (which plenty of technologies can't say).
Re: Building all of our new mobile apps using React Native
#99Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
> Honestly I think the future of mobile will just be... mobile websites. This. Having to install software on my phone to use a service is cringy as hell and is a huge red flag for me. Like when trying to order food from a restaurant or shop somewhere. It's almost always going to be a automatic no. I just don't trust them. They always want permissions to access things on my phone, which is just pure nonsense. It's goi…
I agree with the overall points, less so the pointless vitriol. Installing software is cringey as hell now?
The main issue here isn't native apps. It's the existing framework for installing them.
For instance, would it be that far-fetched to be able to open an app in a single click?
Current extended process: 1) Click link that takes me to app store page 2) Find and click install button 3) wait 4) Click "open app" button
Streamlined process that accomplishes the same: 1) click link 2) wait 3) app opens up (download/install hidden behind spinner)
Even if you have to add a pop-up in there to display permission requests, it's still a much smoother experience.
You'd have to worry about app sizes but that's a solveable problem as well.
Re: Building all of our new mobile apps using React Native
#100Why do they begin justifying by talking about 70% of buyers using mobile? Completely off topic