One big app, or multiple smaller ones?
Hello everyone,
I built and maintain an app for a nonprofit that organizes two weeks of events every year. They are quite happy with it, but want more functionality. We have to stick to appsheet because that is included in their license at no additional cost (and they cannot afford to pay anything), integrates well with their workspace and is in theory easier to maintain. Currently, it has these functions:
- staff lists and management
- enrollements
- participants overview and relations
- finances
- event management (days, activities, tasks).
Currently, there are almost 40 tables in the app, with some more slices. Developement can be done by one person at a time, and the amount of data, actions, views etc. Is growing so large it becomes harder to maintain a good overview. I have started to more rigorously standardize it and minimize the amount of tables and views needed, but that has an obvious limit.
They also want to expand the functionality:
- from basic finances to a full replacement of their accounting sheets
- expanded event and task management
- better rbac for pii (essentially splitting off pii into separate tables)
- crm for businesses and employees
- system to manage purchaces, offers
- basic inventory management
This is probably too much for one appsheet app. I know you can crosslink to other appsheet apps.
Question:
- should i split it up into many focused smaller apps, or a few bigger ones?
- what are the logical candidates to split off? I was thinking of at least splitting of finances and inventory management
- how do i keep a unified ui for the user, so it is close to a single app experience?
Any info, tips or resources are much appreciated.