Hi everyone,
I know this is very difficult to answer but I will do my best to provide enough background. 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. 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. 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. 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? Did I make a mistake not splitting PO's and sales orders/invoicing to a separate app? 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
------------------------------
Question
Recommendation on App Structure - Separate App or not
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.