What is the most convenient way to design the storage of data in the application, with the possibility of updating / adding them?

Question

Android

Hello!
I have little experience, I made only a few simple applications, without publishing in Google Play.
Now I want to make a convenient application that can be popular and on which, theoretically, it will be possible to earn some gold in the future. I'm looking for a maximum of 500,000 users, but it will be quite a challenge to make any money on it, especially with the first application for google play, so my budget is minimal.
A simple application with (static?) text content for Android, without any authentication or other complications.
The application is launched, a list of content, detail pages and other similar screens appear with purely front-end functionality, i.e. without the possibility of sending / changing the user of any data to the "main" database (because each database has its own) and without the possibility of interacting with each other.
The question arose about storing data and their subsequent updating / deletion / addition.
I read several articles on this topic, I realized that there are several options:
1. "sew" data directly into apk
2. load all data over the network
3. combined - "sew up some basic part", and load only when updating / adding data
In my opinion, the 3rd option is the most convenient, but I rejected this (and the 2nd) approach, because I don't want to spend on hosting, server, backend or backendless services, because, in the end, it will have to be spent anyway.
Maybe I'm missing something, maybe I don't know any approach to solving such problems, I don't want to completely make the application, and then it turns out that there are some restrictions in Google Play or that the application will be very inconvenient to maintain and update?
Is it realistic and reasonable to use method 1, and what would be its disadvantages?
I will also be very happy with links to resources / books / courses specifically on designing commercial applications, with good architecture and various approaches for solving problems for Android.

Answer 1

Only one drawback is the large initial size of the application if there is a lot of data.
In general, for any "content" it is best to store data locally, and update the database with updating the application itself in gplay.