Live data from Hacker News

Building all of our new mobile apps using React Native

engineering.shopify.com

541–550 of 588 posts

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

#541

Earlier quoted context omitted.

Without synchronous view layout, it's not really possible to have a truly recycling view without many warts. We've (Wix) been hacking at this for years, and it's not possible. You either block the UI or view flash for the user if fast enough scrolling is performed. Facebook engineering promised synchronous layout will come at some point, which will open the door to that.

What about Flipkart's https://github.com/Flipkart/recyclerlistview ?

No web-only solution will give you a fully satisfactory result. It's just not possible. If you scroll fast enough, you will see either flickering or empty zones.

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

#542
post #506

Earlier quoted context omitted.

I don’t understand your comment. I have other sources of revenue, mainly doing development for customers. I didn’t bet everything on that app and raised money on the expectation this would be a gold mine. I’m just stating a fact : without those 30%, in my present situation, i could live only based on this app revenues. With the 30% cut, i can’t.

I’m sure most people could live off of less revenue if they didn’t have any expenses. But, a niche product where people aren’t willing to spend money is a business model problem.

That's one way to look at it. All businesses come down to balancing income with expenses indeed. All i'm saying is that 30% cut on the income by apple makes it harder , and sometimes impossible , for some business model to survive.

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

#543
post #486

Earlier quoted context omitted.

Unfortunately I can also provide several items of arcane knowledge for Android and iOS. So should we now measure who wins in arcane knowledge counts?

Yes. We could. The web would lose hands down. The Web lacks even the most primitive of UI primitives that desktop and mobile UI kits have had for decades . Virtual lists is the prime example. You can't even reliably animate an element independently of other elements without breaking your entire page. You can't pick an arbitrary group of components and place them in a different location of the page without them breaki…

Sure you can animate, that is what WebGL and SVG allow for.

Ah, like breaking Android UIs when dealing with fragment management or misplaced constraints on ConstraintLayout, usually only solvable after one finds the golden post on medium?

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

#544

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…

I really like the idea of PWAs, but I've tried a few of them and I always come away being annoyed at the app launch latency. They still feel like they're hitting a remote server when starting up for.... something? My uneducated hunch is that they're over-zealously checking their server for updates. The other issue I have with their implementation is the opaqueness of how offline caching works. How much space do apps…

This is a solved problem via service workers. They can cache all the app's content and you can choose to cache whatever you like including api responses from any service. They could also be configured to serve cache first and replace the content in background. At this point if the app is slow to start, it's 100% on devs/architecture. The only problem is if you exceed the quota for cache, which is varied by browser/platform, you risk the browser just nuking all your cache/localstorage/indexeddb.

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

#545

Earlier quoted context omitted.

What about Flipkart's https://github.com/Flipkart/recyclerlistview ?

No web-only solution will give you a fully satisfactory result. It's just not possible. If you scroll fast enough, you will see either flickering or empty zones.

there are demos - https://github.com/Flipkart/recyclerlistview#demo

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

#546
post #542

Earlier quoted context omitted.

I’m sure most people could live off of less revenue if they didn’t have any expenses. But, a niche product where people aren’t willing to spend money is a business model problem.

That's one way to look at it. All businesses come down to balancing income with expenses indeed. All i'm saying is that 30% cut on the income by apple makes it harder , and sometimes impossible , for some business model to survive.

Understood.

But do you know how many businesses would die to be able to sell products that had a 70% gross profit margin?

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

#547
post #375
post #43

Earlier quoted context omitted.

Apps are dominant on web because, well, the web sucks. We can gloss over this on desktop because of raw processing power but still, layout if html is just plain terrible. Of course mobile processors will continue to improve but on mobile you’re making a trade off between performance and battery life and battery life will probably never be not a concern.

The mobile web sucks because of ads and bloated websites not because some inherent technological flaw.

And because of the "separate sites" approach to mobile web development. Good for some media-focused applications, but usually the separate mobile site has an oversimplified interface that can't be zoomed in or out.

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

#548
post #436

Earlier quoted context omitted.

You think all of those are inherent flaws of using a webview? Some of those are because the developer didn't implement them (transitions, dark mode) and others are because Apple didn't implement them in WKWebView to follow the OS behaviors (cursor, keyboard). Not sure about your comment about the text size or the display artifacts.

Not really interested in tracking down who is responsible for what. My point is that literally every single time someone comes along claiming that their hybrid framework or app is indistinguishable from native and I go check it out, it’s obvious within 30 seconds that it’s a poor substitute.

We are in a conversation about the future, most of which seems to be being held back by players who have a vested interest in keeping people using native apps; so while you might have the "we are already there" conversation a lot, your knee jerk response doesn't really have a place here.

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

#549
post #200

Earlier quoted context omitted.

Perhaps I'm misunderstanding the logic but doesn't that mean using a fancy pen is "cringey as hell" since you can just use a simple ballpoint pen? Sorry, it just seems unnecessarily negative to me.

Yes, you are misunderstanding the logic. A normal web app doesn't need to be installed, disappears each time you close it, runs in a tight sandbox. Much better and lighter than have an app installed. Besides, I do find fancy pens cringey, but that's another story :)

haha fair enough. Thanks for the clarification!

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

#550
post #304

Earlier quoted context omitted.

Perhaps I'm misunderstanding the logic but doesn't that mean using a fancy pen is "cringey as hell" since you can just use a simple ballpoint pen? Sorry, it just seems unnecessarily negative to me.

It's like you ask someone if you can borrow their pen, and they say "Sure, but only if I can rifle through your wallet and attach this GPS tracker to you"

This sounds like you're implying that all apps must require invasive permissions which is wholly incorrect.
Post reply on HN