Efficient Maintenance Strategy for Multiple Similar Applications

Ask for Help
1

Hi friends, I feel like I need to ask for your input on how to efficiently maintain 8 applications that I will develop. These eight applications have 50% similar content and the rest is unique for each application in terms of data (not design). Some scenarios that come to mind are:

  1. Keeping them separate so that if there is a problem with one application, it does not affect the others.
  2. Keeping them separate, but consolidating shared data in G. Sheet using Google’s methods (app script or formula).
  3. Using a single G. Sheet data source while keeping 8 applications.
  4. Building one large application but it will be complicated in terms of managing its visibility settings.

Or are there suggestions for using other methods?

2

Is there a reason you don’t use Glide Tables and sync the table to different apps?

1 Like
3

Wait…, I might be missing something. What kind of sync are you referring to?

4

I would build multiple Apps using shared Glide Tables. Only attach Google Sheets where it is absolutely necessary.

1 Like
5

Yes, I’ve limited the use of Google Sheets. I’m not clear on how Glide Tables can be shared between apps.

6

There are two ways.

  • You can duplicate an existing App, choosing the “Keep same sheet” option. Both Apps will then share the same set of tables.
  • You can link an existing table to an App from the Data Editor:

CleanShot 2024-02-15 at 09.52.59@2x
CleanShot 2024-02-15 at 09.52.59@2x694×592 39.6 KB

2 Likes
7

Oh, I just realized this option.

I’ve used this method before, and perhaps this is why when I deleted one sheet, it also disappeared in the other app.

8

If it was a Google Sheet, then yes that would happen.

Glide Tables shouldn’t allow themselves to be deleted if they are used in multiple Apps. You would need to unlink them from other Apps first.

9

OK …
Is there an option to unify apps (not data tables) but changes in the design/layout of the app, so I don’t have to make adjustments for every change in each app?

10

Unfortunately, no…

Getting back to your specific use case (8 Apps), I would probably build the most complex App first - or at least the one that has the most in common with all the others. Then you can duplicate that one multiple times to create the others, and remove the UI bits you don’t need in each one. This will help minimise the work involved.

11

Got it, this is what’s currently being done…
Thanks for the suggestion, @Darren_Murphy and @ThinhDinh .

1 Like
12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.