![]() ![]() We can only commit to reduce by how much we'll miss it by. In the end, I say yes: but only on the condition that we are not committing to making the deadline. Not unless we cut the scope, push back the timeline, or add more people. I've seen enough to know that we are up against an impossible task, so I replied with the only sensible answer: In an unexpected twist of events, my manager asks me to take over leading the Amsterdam part of the project, given both my background and some of the early contributions. And without Payments working, the launch would be delayed. Our features won't be ready for the 16 September launch. "We" - meaning the Amsterdam payments team. On the second week, I'll attend Uberversity - Uber's mandatory onboarding "bootcamp", where I'd learn about the business.Ī few days into my stay at HQ, I am called to an emergency meeting. The plan is to work a week from the office and get to know the US teams. Middle of August, I board a plane to the Uber HQ in San Francisco. "I don't think I knew what I signed up for" - I tell my wife. "This will be fun" - I say confidently to my new team. To make this deadline of 3 months away happen, we need Android and iOS engineers. So we need a stable version of the app by 24 December. Why 16 September? It's because of counting backward.Īpple freezes the store at Christmas. Apparently, most people forgot about this announcement, but not TK. I hear stories of a party at Las Vegas at the end of 2015, where TK announced that a new Uber app will be on the store by the end of next year. ![]() I am still getting my head around all of this. New UX, new workflows, different screens - and a new architecture and language, behind the scenes. Uber's Rider app rewrite in 2016 (Helix): it completely re-imagined the app. Every last screen of the old app will not only be ported, but re-imagined, UX and workflows changed. We have less than 3 months: the rewrite needs to be done by 16 September. For the program teams - the ones building features -, the work started a few weeks ago. The mobile platform team has been working on the project for a few months, coming up with RIBs, a new architecture we're using for the project. Hence me joining the Android team over the backend one. Over 1M lines of code per platform, with more than 100 iOS and 100 Android engineers working on the project. We're rewriting the Uber app: the whole thing. ![]() On week one, I get the scoop on the unusual and last-minute request. (Little did I know that I would not have written my book Building Mobile Apps at Scale if this last-minute request did not come in). I say yes, though I'm a bit puzzled at the request. I've done Windows Phone and iOS before - Android would be the first. He can tell more details when I've joined. Two weeks before my starting date, my manager emails me to ask if there's any way I can do Android. My interview process was messy, and although I thought I was interviewing for a mobile role, I ended up on a backend interview loop and getting a backend engineering offer. I'm be moving to Amsterdam, joining a team building Uber's payments systems. Valued at $62.5B, the company does not seem to be slowing down.Īnd I got an offer to join Uber as a senior software engineer! Uber has been dominating headlines: the company on a rocket-ship growth trajectory and is changing the way people get from A to B. This is my story and some of my journal entries from the time. However, Helix - Uber's Rider app rewrite in 2016 introducing Swift and RIBs - stands as the craziest project by a margin. I've worked on many projects throughout my career as a software engineer. Menu Uber's Crazy YOLO App Rewrite, From the Front Seat
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |