You are currently browsing the tag archive for the ‘datamodel’ tag.
Builders Invoice Mobile App
Lets say we want to create an app for a home Builder / Carpenter – they need to quickly make up an invoice on their mobile tablet, while onsite at a job.
The different things to keep track of are :
- Job / Invoice
- Invoice Line Item
Step 1 : Define the ‘DataModel’
We define all the properties for each of these :
- Customer : Name, Address, Phone
- JobInvoice : Date, Description, link to a Customer, list of InvoiceLines
- InvoiceLine : a Product, an Amount, a Cost Total
- Product : Name, Description, CostPerUnit, Units, Photo
I’ve shown the relations in bold, where one item refers to another item.
Step 2 : Run the App
So you just click thru and define the ‘DataModel’ above, and then you can run the app and try it out immediately.
For this Builders Invoice datamodel, the app looks like this :
Quick and Iterative
The immediate feedback is really useful. You can show a user, get them to try it and give feedback. You can try out different models and see which fits their business better.
This iterative approach really helps to reduce risk and cost in developing an app.
We could have picked any domain and modeled it in the same way with CollabAPI. Its not about Invoices .. its about making an app to fit your particular business : quickly and iteratively.
If your business finds it helpful to have a photo in each InvoiceLine, to give the customer more insight into the Job .. so be it.
When you business changes, you can change the datamodel to fit the new circumstance.
I hope you’ll agree, CollabAPI takes a pretty radical, and yet very practical approach.