Recommendation on App Structure - Separate App or not

Question

Hi everyone,I know this is very difficult to answer but I will do my best to provide enough background.&nbsp; I am trying to understand how much functionality to build into one application vs time to split it...I have one app that has CRM functionality and Project Management functionality built in and very much tied together.&nbsp; In addition it has sales order, PO, and functionality all built in as our projects require all of that.I now need to add functionality for smaller orders.&nbsp; So lets say someone has to buy a single piece of equipment, it is not necessarily an entire project so we account for it differently.&nbsp; However, it still has CRM related data, as an opportunity, sales order, PO, etc.But it is all handled slightly different vs projects.Am I better off making a completely separate app knowing there will be some duplicated functionality?&nbsp; Did I make a mistake not splitting PO's and sales orders/invoicing to a separate app?&nbsp; Do I need to rethink that?Or do I just layer this on top of everything else and hide via security settings the functionality some people will not need.------------------------------Ivan Weiss------------------------------

markshnier__you · Answer

My natural inclination would be to try to use form rules and hidden section to maintain just one App. Inevitably there will be situations where you will need to have consolidated reporting and you will also want to avoid the duplication of the main tables. While this can be done with Sync tables and cross app relationships, I suggest that the simpler and less maintenance intensive route in the long term will be one app.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------

ivanweiss · Answer

Thanks Mark, I was leaning in that direction but didnt want to go down a path without hearing some recommendations------------------------------Ivan Weiss------------------------------

austink · Answer

It depends how big you expect it to get and how many different roles you have at your company. An app I work on currently has almost 100 roles in it because it was never split and has grown into a monster. We are currently trying to split parts off into their own app because of this. It is very difficult to do this at this point but it just needs to be slowly done. It is a nightmare trying to navigate all the different form rules for all these roles. They don't all work in the same place but there is a lot of shared work in here.

ivanweiss · Answer

The problem with us is everything is so inter connected. I am thinking the way to go is this main app, a separate app for HR functionality for security reasons, and potentially a third app for a built in knowledge base.

------------------------------
Ivan Weiss
------------------------------

markshnier__you · Answer

That makes a lot of sense to me. Your original question had to do with separating large orders from small orders but now you are really talking about separate functionality For a very different audience users.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------

Forum Discussion

Recommendation on App Structure - Separate App or not

Related Content

Design Recommendation Needed

Separate variables

How should I structure my tables?

Sort & Group separate from UI

Contact Form Recommendation