How should i structure my app?

AppSheet AppSheet Q&A
,
1

I basically have 3 different centers which I manage in the same locality. But I have 3 different app for each center.

Lately I have been having a thought that the database has to be centralized. So there should 1 customer app. And then a separate booking app, where I can book a service under the customer basis the center being visited and basically work by linking these 2 apps.

But I am not too sure is that right way to go about or I should continue with each center having separate apps. Also the customer database along with pet photos and documents being around 15k, not sure if appsheet can handle the same.

I can rely on some guidance for this…

2

Generally speaking, when dealing with shared data, it’s easier to develop one larger app than multiple smaller apps, but there is also substantial added complexity. What the apps do, who the users are, and what data is shared play a huge role in choosing the path, as does the developer’s skillset and comfort level.

3

Thanks for your response Steve. I am actually in a fix. Having one common customer app linked with other bookings app will help me streamline my data but at the sametime complexity us increased.

Till now I have been having different app for each center..but in terms of maintenance it becomes double the effort.

I am not sure on how to come to a conclusion.

4

Myself, I prefer a single app to multiple apps. But with a single app, you have to consider how to limit each user to only the data and features they should be allowed access. That can be a complex problem to solve. Were I in your shoes, I would start a new app with its own data sources. I would populate those data sources with sample data from the live apps for testing as I develop the new app. Then, I would start implementing the features of the live apps. As I implement anew, I’d be thinking about making sure the feature is available only to whom it should be. Access control can be a complex challenge. The community can certainly help.

1 Like
5

Hey Steve,

Do you mean I should have 1 customer app, which should further connect with a booking app?

6

Nope. One app, period. Create a new app that will be the one app that replaces the other apps.

7

But my issue with that is with respect to scalling…I am afraid the app wont be able to handle it. Because there are separate modules involved like inventory etc..

8

The only way to find out is to build and test it.

1 Like
9

Understood Steve. I think I am just too afraid to try because of the work and responsibility that comes with it if it fails.