Fire. React native is the best for your use case when you eventually make the change.
At some point once the app gets more complicated look into ways to seperate the business logic from the UI logic. You can write the business logic in any language you like, and then expose it through APIs, or something like function app on azure or lambda on AWS and call it in your UI code. At that point you'll be ready for two code bases too and be able to use fictionality specific to Apple or Android.
But that's way down the line. Most important is to keep it simple for now. And I assume you don't enough business logic to even seperate it for now so that's a good move too.
I get paid to review architecture of apps before the green light is given to write a line of code. With a high level understanding of your app, I would say you made all the right choices. That's not knowing how you access the list of different stores. If you adding them to a database and then connecting directly to the DB, that's cool at this scale, but look to add an API layer. App hit API, API hits DB, DB returns to API, API returns to App.
But most important thing is to understand your scale and not overcomplicate and to me it looks like you made all the right decisions.
Fire shit fam.
Hoping for nothing but the best.
Always feel free to DM if you have high level architectural questions and I got you.
