101–110 of 221 posts
Earlier quoted context omitted.
Android performance is garbage. Source: just downloaded app.
I call BS. I just downloaded it and it works fine. Literally every single one of your comments has it out for this transition. I trust my own experience and their data.
And define "fine" first. If you mean that it works, sure. But it works slower than truly native application, like Telegram.
Earlier quoted context omitted.
What a trope that AirBnB story has become. They mixed their gigantic native codebase with React Native code. Mixing native and React Native = bad. Doing pure React Native (for everything but ultra high-performance and apps that interact tightly with hardware) = good.
I remember there were a ton of articles and hot takes around that time that dunked on RN with zero context, essentially saying that RN was dead because Airbnb couldn’t crack it. I feel like all those takes completely misunderstood or ignored Airbnb’s technical constraints and the underlying reasons. Anyone blamed it on the library. Not the dumpster fire implementation that ultimately killed the venture
Long story short, terrible idea unless you're in a position like coinbase. The article is from a high level engineering standpoint about productivity and trying to be efficient. The thing the article doesn't mention is the best react native developer also is an expert in native mobile development. It is crazy hard finding these people. All techno fluff aside, any component mobile developer knows once you have a solid…
What an attrocity. You could've just said that you no longer want to invest in mobile talent. Just opened Coinbase Android app: * Overall slow * Jank in transitions * When dialog pops up and you close it, there's a dangling shadow in the air * You open privacy policy and application is killed in background and you see splash screen again with no state restoration, what the f? Hot garbage, the time you spent on this c…
What has gotten you so upset about this transition? I don't understand. All your comments are so vicious with no backing. >You could've just said that you no longer want to invest in mobile talent. How does this even track? They had to retrain their engineers. I call complete BS with your app experience. I have a Redmi and the app works flawlessly. They seem to have internal data to prove it. They were under no oblig…
I literally listed my experience with the app. And I didn't even create account yet.
> How does this even track? They had to retrain their engineers.
To leverage Web developers, right.
> I call complete BS with your app experience. I have a Redmi and the app works flawlessly.
Which Redmi? I'm testing on Xiaomi Mi A1. It probably works better on my Samsung S10. But then majority of people have phones closer to my Xiaomi.
> They seem to have internal data to prove it. They were under no obligation to make the blog post if they didn't think it was successful. If anything they are going against the grain here so they know there are lots of people watching.
Because the blogpost makes it seem like there are only upsides to technology and the only downside is that it's not fit for brownfield.
I had very bad experience with RN and give my opinion on tech. What's the problem?
Earlier quoted context omitted.
> Every 5 or so years there's an "important" transition happening. Name at least one change in Android SDK that can come close to revolution that is Compose. And same for iOS/Mac and SwiftUI. Compose and SwiftUI are doing to mobile what React did to web. It arguably single most important change that happened since the inception of mobile platforms. > There's been many stories written about companies that live on the…
I agree the current one is a major change but it's not mature yet. It hasn't stood the test of time. Twitter was built on RoR when that was the coolest new thing to build things on and Uber's booking engine was on Node.js when everything was being run on Node. I'm sure there's more I'm missing. .
React certainly stood the test of time.
Earlier quoted context omitted.
No, they didn't address anything. They only said that it didn't work for Airbnb because it wasn't greenfield. The real reason it doesn't work out, is because React Native is a dumpster fire. If you really want to go cross platform way, then go with Flutter or wait for JetBrains Compose to target iOS.
Oh yes. You know best. Their CTO did no due diligence before making such an important transition. They didn't even bother talking to AirBNB about their experience. Nothing has changed since AirBnB made their transition. You my friend, know all the ins and out more than the silly, tech illiterate Coinbase team.
He certainly didn't do enough of it, right. They have traded long term prospects for short one.
In the long run you'll have more issues with React Native than upsides.
They cited issues with hiring native mobile devs, well now they've made it even harder for themselves. Since they need to find devs who know both native and React Native. And those guys cost even more than pure native devs.
That's actually a good idea for a career. Learn native, React Native and make big buck from companies that are stuck with React Native.
Long story short, terrible idea unless you're in a position like coinbase. The article is from a high level engineering standpoint about productivity and trying to be efficient. The thing the article doesn't mention is the best react native developer also is an expert in native mobile development. It is crazy hard finding these people. All techno fluff aside, any component mobile developer knows once you have a solid…
Fun fact - your new word "aplkenabd" is a one-hit wonder on Google! What was it meant to say?
Earlier quoted context omitted.
Oh yes. You know best. Their CTO did no due diligence before making such an important transition. They didn't even bother talking to AirBNB about their experience. Nothing has changed since AirBnB made their transition. You my friend, know all the ins and out more than the silly, tech illiterate Coinbase team.
> Their CTO did no due diligence before making such an important transition. He certainly didn't do enough of it, right. They have traded long term prospects for short one. In the long run you'll have more issues with React Native than upsides. They cited issues with hiring native mobile devs, well now they've made it even harder for themselves. Since they need to find devs who know both native and React Native. And…
This is extremely presumptuous to say the least. It assumes they didn't do enough and that you know more.
Earlier quoted context omitted.
Oh? You know everyone's salaries?
I don't see shortage complaints from FAANG companies.
It's pretty common knowledge that FAANG pays really well. One of the big reasons people work there are for the extremely generous salaries. Everyone else is underpaying if you're comparing them to FAANG. Also by your definition, Apple and Amazon are notoriously cheap too. Really you're only comparing to Google, Facebook and Microsoft (less so).