App relationship design philosophy
I'm interested to hear opinions from experienced Podio designers about app relationship design. In particular rules for which way around to do the relationship referencing.
For example, I downloaded the Basic Project Management pack and was surprised to see that deliverables have a link to projects and not the other way around. In my mind Projects 'contain' deliverables and I would have designed the Project app to have a relationship field for deliverables. Referenced that way you would add deliverables to projects, rather than add deliverables in the deliverables app and then reference each of them to the relevant project. What are the advantages and disadvantages of setting up the referencing each way?
I appreciate that if you reference deliverables from project and have a large number of deliverables then the project app will stretch out with a long list.
-
Hi Mike,
if you have only one App for all projects and one app for all deliverables of all projects I would recommend to set the relation from deliverables to projects. Cause if you want to filter the items in deliverables app (e.g. show all deliverables for project x) you can only filter on outgoing relations, not on incoming. I think, this is the most important criterion for the decision in which way you set the relation.
Rainer
Please sign in to leave a comment.
Comments
2 comments