141–150 of 221 posts
Earlier quoted context omitted.
This is the error that most web devs make. Their definition of fine is so low, that they can't comprehend reasoning why web tech is inferior on mobile.
LOL. So now my standards are not high enough? Everyone should program in C. Definitely one of the fastest. So we can all serve your highest standards.
Just when there are two arguably most important migrations in mobile world happening(Compose and SwiftUI), they decided to migrate to inferior tech.
Earlier quoted context omitted.
Presumptuous is to think that their decision is impeccable and that I don't know shit when you have no idea who I am and what I do.
I never once said that their decision is impeccable. in fact I mentioned it probably has draw backs. What I did say was you don't have enough information about the decision making process and thoroughness. They cared enough to talk to the AirBnB devs which highlights how thorough they attempted to be. > I don't know shit when you have no idea who I am and what I do. Your words not mine. Re-read all of my responses wi…
I think you're right. In their case this was the best course of action, unfortunately. Not every company has capacity to do things right.
React Native does suck big donkey though.
> Thinking from this perspective led us to... > the average mobile engineer’s velocity remained stagnant > this could dramatically reduce our overall staffing requirements...also have to deliver improved quality and performance for our customers Honestly it sounds like Coinbase is quickly turning into a shitty place to work. Sounds like all the ingredients for a race to bottom in culture. It's so easy to tell that th…
"But we all have to re-qualify for our jobs every year. The red-queen race of Shopify's historic 40% or better growth is that everyone has to show up at least 40% better every year to qualify for our current jobs. I expect you to hold yourself and your teams to this standard."[0]
> Thinking from this perspective led us to... > the average mobile engineer’s velocity remained stagnant > this could dramatically reduce our overall staffing requirements...also have to deliver improved quality and performance for our customers Honestly it sounds like Coinbase is quickly turning into a shitty place to work. Sounds like all the ingredients for a race to bottom in culture. It's so easy to tell that th…
For a basic CRUD app with simple data visualizations, this doesn't seem to be a huge issue compared to apps that might need to take advantage of whatever new capabilities arrive on mobile phones, though those have largely plateaued in recent years.
I've been doing a RN app lately after not using it for almost two years. It's still a very fast way to iterate on both Android & iOS but it also still feels extremely brittle. I've tried and failed to upgrade to the latest version of RN several times now but every time gotten tangled up in dependency hell. I also haven't been able to get it to build on my M1 Mac at all. RN is good for fast prototyping and market valu…
If at all possible, I can't recommend Expo enough. I hated building RN apps prior to it, and now I hate building apps without it.
Earlier quoted context omitted.
I highly disagree that an expert RN dev also needs to be an expert mobile dev. Articles like these make it seem that react native development requires native knowledge but that simply isn’t the case. With almost all greenfield RN apps, 99.9% of the code is RN and only very specific feature are helped out by native code.
You don't need to be an expert in native to write a RN app. However, you need to be very capable in native to have a responsive, performant, smooth RN app, and to keep it that way for years. Large teams can afford to have a subset of platform devs and a large body of RN app devs to make this plan work (note: you now have 3 platforms: iOS, Android, and RN itself). Smaller teams will struggle. Most often, small teams w…
This has been my experience as well. I work on an app that supports multiple generations of iot products. We were forced to start developing for the next gen product in react native, and let the legacy stuff just use the exiting ios and android codebases. We made it about 9 months before throwing out the react native work and porting it all back to native. Management doesn't realize that moving to react native doesn't mean you now only have to support 1 platform, it means you're now supporting 3.
Does anyone know if Flutter was in the consideration set? It's gaining some momentum as a slightly more stable crossplatform ecosystem to React Native. but of course, there is the prospect of Google and Dart.
Earlier quoted context omitted.
Most teams don't hire a "mobile developer", they hire an Android developer, and/or iOS developer, and/or React Native developer, and/or Flutter Developer. So unfortunately it requires some commitment, don't do all of them at once! - React Native: Easiest to learn, good build tools/ developer experience, good amount of jobs already. Unfortunately, React Native is naturally intertwined with JS/ react, so you'll face is…
Could elaborate on why to avoid expo? I found it super easy to use when I dipped my toes into RN development. Also, what alternative are you suggesting?