Many consultants, including myself, opt for the method you initially outlined: developing the app within our own account and transferring it to the client once the initial version is complete.
- One improvement on this process is to ensure that the client grants you editor access to their data sources, enabling you to make changes and updates efficiently without the need to continuously request permission.
For ongoing support and enhancements, I prefer to structure a separate agreement with your client for each "dev run". This can involve setting up a new scope of work and providing a quote for each subsequent development phase they request.
- Clients often appreciate this setup as it allows them to incur costs only when they need additional work, rather than committing to ongoing charges that they may find unnecessary at times.
Regarding retaining ownership of the app and billing clients for usage, while this model simplifies administration and provides a residual income for continued support, it's important to consider:
- Client's desire for data sovereignty and app ownership.
- Potential scaling complexities as your client base grows.
- Liability risks related to data security and app performance.
- Some clients' preference for a one-time cost structure instead of a subscription model.
It’s essential to weigh these considerations and discuss them with your clients, balancing their need for autonomy and ownership against the ease of ongoing support from maintaining control over the app.
For more detailed strategies on managing major updates when you have active users, I recommend watching the "How to manage Major Version Updates (when you have users in the wild) || AppSheet Explained" video. This video provides excellent insights on how to use actions like (Force Sync), communication strategies for planned updates, and the use of [Temp] columns during the transition. These tips are invaluable for ensuring a smooth update process that avoids user interruption.
____________________________________________________________________________________
Ultimately, the decision on how to manage client apps should align with your business model, your clients' preferences, and the complexity of the app enhancements needed. Open and clear communication with your clients about each approach’s pros and cons will help establish a mutually beneficial working relationship.
- This, of course, is only my opinion and I know other devs out there have taken the subscription approach; I'd be curious to hear their thoughts on the matter.
LinkedIn
Twitter
