Also it's not really easy to prevent against such security things with small teams if you can't rely on the tooling inside your language. Building Crypto things is really hard. So People needing to rely on. Today I've rewritten a authentication / authorization layer for one of our internal Apps, now the App is hardended against csrf, timing attacks and many more things. The only things that I used was the internal PBKDF2HmacSha256 for Passwords of Java Sha256Pnrg for Salts and I copied behaviors of the Auth0 JWT Library (i just used another json implementation which the app already had) and i have something like 200 Lines of Code. It's secure as long as MessageDigest and the PBKDF2 Code of Java is secure and that's something people can't avoid. Especially in small teams.
Nowadays though, as long as you have a good idea and some reasonably basic skills, you can make an app for millions of people.
With a customer facing transaction based service like Uber this would be hard. But pocket is pretty straightforward.