Hacker News new | ask | show | jobs
by jessepollak 1857 days ago
Hi all - I support all Retail engineering at Coinbase and was one of the folks who helped shepherd this change through from inception to rollout.

I'm happy to answer any questions that folks have - just thread here, and I'll either answer or pull in our team to give more detail.

4 comments

What does your CI/CD look like? It took me a long time to fully flesh out a RN pipeline that was (mostly) completely automated. Are you leveraging Fastlane? Are you buliding both Android and iOS on OSX VMs? How do you deal with shipping canary versions and is that process also automated? Thanks!
We talked a good amount about this [here](https://twitter.com/dan_coff/status/1393599897119592456). We are using Fastlane. We are building iOS on OSX, but Android on more standard EC2 hardware. We ship canaries with every commit to master, fully automated.
Not really a question but more of a statement that Discover also transitioned from Native to React Native successfully and I believe they also didn't do a brownfield implementation. There was a presentation about this at React Chicago but I can't seem to find it.
So what is your native mobile engineering team doing now?
All of them were cross-trained to be React Native engineers. Many of them are now working full time in React-land doing product engineering and some of them are working on lower level native infrastructure. We saw very little attrition and have emerged as a stronger, unified client engineering group (across mobile and web).
Which native mobile engineering team?
The ones that were initially hired to work native Android / iOS?

We’re they down sized? Re trained? Etc. and so on. Can you speak about the process around this and so on. I understand you want to give a positive image externally here, but I’m more interested in what struggles occurred and how you resolved it / did not resolve it.

Sorry, I'm not the OP. I just tried to be funny. As in "there's probably no such team anymore".
Sup Jesse!
Hi!