Live data from Hacker News

Building all of our new mobile apps using React Native

engineering.shopify.com

381–390 of 588 posts

Re: Building all of our new mobile apps using React Native

#381
post #259

Earlier quoted context omitted.

My point is that it's not a problem. I can take someone fresh out of bootcamp with a basic understanding of react components and css and get them churning out code that works on 3 platforms.

Good luck with that kind of project.

[deleted]

Re: Building all of our new mobile apps using React Native

#382
post #202

Earlier quoted context omitted.

That really just says it all doesn't it? It's basically an admission that the use of cross-platform frameworks is worse for customers/users, but they're going to ignore that to optimize for their own software engineering org.

you act like whatever something is right now is the same in the future. It's quite possible they see RN as the future for all products and easing there way into things. Maybe they are struggling to find Java/Kotlin devs and have a surplus of Swift devs. So no, that does not really just say it all.

I think you’re touching on something extremely important here. IME, anecdotally, not backed up by data: experienced native Android devs are getting harder and harder to find.

The ones I’ve known personally hated it so much they moved to backend or full stack jobs.

Re: Building all of our new mobile apps using React Native

#385

Earlier quoted context omitted.

Simply, it doesn't affect me adversely at all. I think you have a misunderstanding as to how many notifications are generated. Today I received: * 3 reminders to eat * 1 security alert (delivery) * about two dozen instant messages between myself and clients * a couple of dozen CI alerts * 3 emails Its easy to have different levels of notifications, and filter message channels. I have less distraction now than I had i…

What kind of reminders to eat are you getting? Like "don't forget to eat?" or "don't forget, this is your plan for lunch"?

I'd assume some sort of "go eat now, it's time" scheme, so he can stay in deep flow without neglecting his food intake.

Re: Building all of our new mobile apps using React Native

#386
post #202

Earlier quoted context omitted.

you act like whatever something is right now is the same in the future. It's quite possible they see RN as the future for all products and easing there way into things. Maybe they are struggling to find Java/Kotlin devs and have a surplus of Swift devs. So no, that does not really just say it all.

> Maybe they are struggling to find Java/Kotlin devs and have a surplus of Swift devs. Based on AirBnB's experience, now you need to find React Native devs in addition to Java devs.

I can see, if you were a billion dollar company, how you’d have an Android infra team to bridge those performance-intensive items, with the UI team doing all their work in RN.

So you can’t be a startup/small shop if you want to do this well.

Re: Building all of our new mobile apps using React Native

#387

Honestly 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…

Users hate web apps, especially on mobile, and it has nothing to do with functionality. Web apps on the App Store invariably provoke angry screeds about how the look and feel is not right. Native apps are even more essential on mobile. On the desktop, web apps just look weird and waste battery life. On mobile, they feel wrong. That difference in feel provokes visceral hatred.

> Users hate web apps, especially on mobile, and it has nothing to do with functionality. Web apps on the App Store invariably provoke angry screeds about how the look and feel is not right.

> Native apps are even more essential on mobile. On the desktop, web apps just look weird and waste battery life. On mobile, they feel wrong. That difference in feel provokes visceral hatred.

They don't have to waste battery life. This is mostly due to poor coding/architecture, instead of "web". Especially with WebGl and Wasm.

Re: Building all of our new mobile apps using React Native

#388

This is an interesting read and may be the full story, and a completely justified strategy. But at the risk of sounding cynical, I'd be interested in any political motivations - if he's a new VP, it wouldn't have been unheard of for unnecessary swashbuckling Transformation Projects to be kicked off under the new regime for no obvious reason. Complete conjecture, I have no inside knowledge, just have seen this happen…

It happens all the time. At a large corporate place I was working frontend at, our dpmt manager spent almost no time with the teams and all time concerned with outout metrics. When his boss looked to be retiring and the prospect came up to get his job, he started a new year by—seemingly with no knowledge of how things were working—by shuffling all the teams based on how he thought people should be organized. He then…

Yep. I'm more than a little sceptical these days when these big projects are announced - especially with new managers.

Re: Building all of our new mobile apps using React Native

#389

Earlier quoted context omitted.

Most of the money being made on the App Store is for in app consumables from pay to win games. You’ll have to forgive me for not shedding a tear for them. I hope Apple Arcade takes a huge chunk of their revenue. It’s not indy developers trying to make a living. The other types of apps that use to make Apple a lot of money are streaming services. But most of those are now not allowing you to do in app purchases. I’m l…

Though we should shed some tears for those who just try to sell their apps and make a living, after already being ripped off for expensive equipment and an annual developer account fee. If Apple would care, it would be possible to charge a smaller commission based on the app category, and to vaive annual developer account fees for verified open source developers.

Apple gear is no longer as comparatively expensive as it used to be -- they aren't ripping you off, they have put a lot of work into delivering different 'gear' to what's available in the rest of the market. Shed a tear for people who buy HP and need a new laptop every year or two. I'm typing this on a 7-year old MacBook Pro, which works better than the day I bought it.

Hosting an app marketplace is not a free endeavour either. They host infrastructure to facilitate all of this, and they review app code in an attempt to prevent malware being distributed by underhanded developers. Maybe they could vary the price based on the use case, but why should they? No one is compelled to publish on the App Store, why complicate their business model to give themselves more work for less money.

Re: Building all of our new mobile apps using React Native

#390
post #360
post #222

Earlier quoted context omitted.

Sounds like the opposite to me. A bug in React Native and fundamental issues in Flutter.

I don't follow. What I outlined were fundamental issues with RN, not with Flutter.

What you outlined sounded like a bug, the Twitter link I posted covered some fundamental Flutter issues.
Post reply on HN