Fb has react. Snap and bytedance seem to have ar/vr roles. At Uber, most mobile work is seems to be product focused and not terribly hard.
What makes mobile work hard? Aren’t you largely constrained to the APIs available on the hardware? Isn’t most computational work done off device?
Hard/complex mobile work isn't based on data or volume imo but architecture and novel implementations. While certain applications must be downloaded ML models, merging photos, managing network requests, and using data input can be hard. Imagine building an operating system. It feels like there isn't a whole lot of meet like need for work like this at Uber right now
Also, there are alot of APIs available. Libraries for iOS and Android abstract away a request but you can directly access and create sockets, apps have access to the OS although they are sandboxed
Been thinking of this also. What dose it mean to be a senior mobile dev. I'll be very disappointed if it just means knowing the framework better. To your question, the first step is to look for apps that are not just json printer but do a lot locally.
I think there are a lot of apps that aren't json printers but the issue is that at big well paying companies, it's likely to be a subset of the work involved. I'd be curious to hear about some of these apps.
Uber makes their mobile work unnecessarily hard with long build times, complicated architecture, and convoluted processes.
But the ribs be tasty
Would love to hear more on this. I remember seeing Uber publish a lot of architecture and pattern info related to Android dev. I thought they must have some really good architecture for the app. Would love to hear a counterpoint