I’ve got beginner-to-intermediate experience with Adalo.
I need to build an app for my friend to maintain a single shop garage. Its basically a project management app where he can quickly create an incoming job and monitor ongoing progress.
Each car gets assigned a workflow (as per the job), which is broken up into tasks. Each task has its own costs, is assigned to an employee. Task status is monitored, and when one task is completed its subsequent employee gets notified to begin work.
I would have a ‘tasks’ collection, with a many-to-many relationship with a ‘workflow’ collection, with a one-to-one relation with ‘jobs’ collection. (ignore the users collection, its not relevant to the problem).
So far so standard.
The only minor difference is to speed up a new job creation, sometimes there are standard job templates (eg. a 10k checklist of items is standard) vs a custom job (only a side view mirror needs to be replaced).
My question is - what is the right way to implement a standard ‘workflow’ template being able to be accessed by app user? I’ve had a look at the template apps, and Coaching & Ordering apps are closest to my use case.
In the Ordering app each menu app is added sequentially, to a single ‘orders’ collection (which can be easily replicated in my app - instead of a menu item I would add a Task & maintain relational consistency). But I’m not 100% convinced its the best / right way.
Ideally my use case would be along the lines of Coaching App - there are a pre-decided set of activities, except that need to be assigned together. In the Coaching App template they’re again assigned one at a time.
What is the right UX (Screens, Lists, Lists of Lists, buttons, ‘Action’, ‘Custom Action’, Create/Update steps) & Database Schema (any modifications to above) I should implement?
I believe this project management is a generic use-case for a lot of applications - logistics fulfillment service providers, event management, coaching etc. and the right solution could help a lot of makers on Adalo.
Appreciate any help.