The first, second, and third thing I would try is dividing up the app. I suppose there are things that might be better off as a monolith, like maybe a really powerful CAD app with an in-memory data model.
But in most cases, where the data model is in a SQLite database, you can put that in a ContentProvider and have multiple apps access it.
"But that's not how we designed it." OK. OK. Just saying. It's a mobile device. It has constraints. It also has benefits for implementers who don't try to just steamroll the limitations.