If you can design 1) the database schema, and 2) the application's frontend (either web or native app), you're essentially a full-stack developer. What's left are the operational details increasingly handled by service providers (like AWS).
While being able to do a first pass of a working app from front end to back end is something many can do, planning for the unexpected, scaling, understanding edge cases and where things may break (including diagnosing problems in off the shelf components), digging deep into AWS issues, etc. Require a depth of skill and knowledge very few can actually achieve across a wide breadth.
Is it possible you're projecting? Ops is vital to launching an app, but it also has little to nothing to do with the development of that app. It's a completely different skill set.
If you spend weeks/months building an app and then launch it and find nobody wanted it then you've just wasted a lot of time and effort.
If you spend weeks/months building an app and then discover you can't deploy it in the way you planned because of an operational detail, you're going to incur a lot of rework.
How long is it going to take you to get your app into production?
If you start right from getting your hello world webapp into a production operations environment, then iterate until you have something you can start testing with users you won't have any of these problems.
You will however, have to start considering operations from the start. There's a lot less waste, it's lower risk, but you can't ignore operational concerns as someone else's problem.