Save App as Template, so I don’t need to rebuild it completely. Even if I tell Cupy to make an exact copy of the App, it builds it slightly differently and some bugs - that I already solved in the old app - are present again.
Your use case
Make a good App once. Re-use it with different datasets. In my case: I have different clients, and want to showcase candidates to them. It would be good to be able to “clone” or “open” a templated app instead of starting all over again for each new client.
In the meantime, if you don’t need to share the app publicly, the quickest workaround is to duplicate the base. When you copy a base, all resources tied to it — including Apps — are copied over as well. That way you’re working from a clean clone of your polished setup, not rebuilding from scratch.
thanks for your soon reply. I will check out duplicating a base. However, I think this is not an ideal process, because one will have 10s or 100s of bases.
Re the other discussion: this is something different. I do not want to publicly share the templates. I only want to “clone” or “save” my own app.
Example: i created an app for a client, where I present candidates AND where we can collarobare in the app.
This app is very useful also for other of MY clients. So i want to re-use this as an internal template.
One thing worth noting on the Share approach: the link doesn’t have to stay open permanently. You can enable it, save a copy yourself, then turn it off — so it works fine as a one-off.
On duplicating: it depends on whether your App is bound to a specific table. If it is, duplicating the base is the cleaner option since everything stays connected. If the App isn’t tightly bound to a table, duplicating just the App should carry over the logic, data reads, and actions as-is.
That said, the best path forward really depends on how your App is set up. Could you share a bit more about your structure — for example, is each client’s data in a separate base, or all in one? That’ll help us point you to the right approach.