Hello All!,
Feeling a little frustrated with the whole non transferability of big tables. 
I’ve made an app for my client which is expected to go beyond 25K rows in 8-10 months. Hence i chose big tables as my data source. My app is ready and I need to transfer this app to them and obviously i’m stuck since big tables cannot be transferred.
I’m sure i’m not the first developer who has arrived at this bottleneck. How do others manage this? I was developing initially on google appsheet(have developed 10 apps there) but switched to glide because the data transfer process was smoother but i guess not! @NoCodeAndy
@david, does glide assume that most client apps won’t need more than 25K rows, ever? Cause at whatever point there is need, not only does the client need to upgrade the plan(which is fine), but the developer would have to come back and re-build the whole database again on big tables, else the app would becomes useless.
hi @Akshit_Agarwal , try creating a template of your app.. publish the template “privately”. copy the private template url, open the url on your client’s team and your app will be duplicated in their team
The recommended approach is to build the App in your clients team from the start. Then this isn’t an issue.
Having these bottlenecks for transferring apps is demotivating for someone wanting to get into the glide experts program.
Because professionally speaking, even if i was part of glide experts program, and my client was on a business plan, i would still have to ask them to add me to their team if data source needed were to be bigtables.
The accepted standard in the app development world is always build in your own ecosystem, receive the payment for development and only then handover the app.
The method you suggested exposes a developer to the risk of being ghosted by the client mid development since the ‘owner’ of the app right from the start is the client.
Yes, and as I said, that is the recommended approach. And you don’t need to be in the Experts program to work this way.
Maybe, but that’s not the way it works in the Glide ecosystem.
That’s never happened to me, and I’m not aware of it ever happening to any other Expert/Agency.
By the way, this is not my suggestion (although I do support it), it is what Glide recommends to all Experts/Agencies.
Glide allows you to create a team with 30 day Business Plan trial. What we all do in this case is, create a trial account (if you have an Agency Plan, you don’t need a credit card to sign up for trial account) and start the development in there. Once the final payment is done by client, we just handover them the account and make them the admin of team.
@Hassan_Nadeem Yes this is also a good workaround. My point is that these workarounds are needed where the ecosystem doesn’t have a ‘handover system’ for the app. Glide does! But given the constraints of data source being only glide tables that can be transferred, developers either resolve to the approach that @Darren_Murphy suggested earlier here (build in the client’s team) or what you suggest where you handover the account. Both are ‘workarounds’ and honestly i wouldn’t have a problem if glide openly says, that their app transfer is only meant for apps that would need 25K rows maximum in their lifetime.
I apologise if i sound a little frustrated but its not without reason because i switched from google app sheet to glide because the transfer process was a pain there but glide (definitely overall better than app sheet) also does fall short on the whole transfer process.
I hope @david notices this and finds this candid feedback as something that can be used to improve the currently limited app transfer process.