two users editing the same DB: is there a workaround?

Hi,

The only way to do this is share the same apple ID. Maybe you can create one just for that purpose?

Dropbox would be a great alternative. I know because the app “The vault” is using it this way and I believe it also uses the same database engine.

Maybe Brendan could look in to this….or not :-)

Leo

Patricia,

mmmmm, yes you need to switch accounts if you use iCloud for other purposes.

The dropbox version is iCloud independent, at least for the Vault. But tis isn’t implemented in Tapforms….yet?

The other work around is to backup your database to dropbox and restore it from dropbox but then again, you doesn’t always have the accurate data and it needs a lot of backing and restoring.

No solution for different iCloud users for now. sorry. Here where are using the same iCloud ID and switch whenever needed to purchase an app.
(Where not using iCloud for mail or contact etc.)

Leo

Hello Patricia,

My apologies for not answering sooner. Thank you Leo for helping out Patricia!

Tap Forms was built with a single user in mind. The original vision started with the iPhone version to try and gather all the stuff you have in your wallet into a convenient place. It has come a long way since then!

I do realize the need for a multi-user version of Tap Forms and it’s definitely something on my radar. There are just so many different ways to accomplish it. Right now iCloud is the only way to share data with different devices. But it’s also a half manual, half automatic process. That is, when you make a change on one machine you need to click on the upload to iCloud button to send those changes up to iCloud. Then a little later on (a few seconds or a few minutes), your other devices will auto-sync those changes.

Adding multi-user support into Tap Forms is more than just syncing the data. Imagine you’re working on a record and someone else changes it right in front of you. Or deletes it! Those kinds of things need to be considered when making a multi-user database.

Dropbox is an alternative to iCloud syncing. The benefit of that as Leo mentioned, is you can have a separate login from your iCloud account that multiple users could share.

So, some customers want multi-user, some want Dropbox sync, some want WiFi sync, and some want their data accessible from a website. There’s a lot of things that I’m working on adding to Tap Forms. I’ll get there over time. But multi-user, WiFi, or Dropbox sync won’t be coming in the next update.

I’m sorry to disappoint you.

Thanks!

Brendan

Hi Ideapool,

I do have some customers who sync Tap Forms with different users. You just have to be cognizant of the fact that there are no security controls built-in to Tap Forms that would prevent someone from deleting something they shouldn’t or mucking about with the form structure.

Having said that, I am working on adding some basic access controls to Tap Forms. Nothing too fancy yet, but it would give you the ability to prevent someone from deleting, adding, or updating records or modifying the form structure.

As for syncing, you can use any of the non-iCloud sync services to sync with different users. iCloud requires everyone be on the same Apple ID and that’s not convenient for multiple users.

But also, even if you were syncing with one of the other methods, every time you make a change, sync happens and that will cause the other devices to refresh, even if the user was typing into a field at that moment. They’d probably lose what they were typing at that moment. Although with Apache CouchDB and IBM Cloudant you can turn off auto-sync, so you can just sync whenever you want.

Thanks,

Brendan

I never stopped supporting Cloudant. IBM just moved it from a separate service to a service embedded within their IBM Cloud infrastructure. Tap Forms still works with Cloudant.

I don’t like to give exact timelines. It’s a feature I’m still working on actually. Right now just working on the user interface to let you enable and configure access controls. I haven’t written the code yet to react to the access controls settings. But that’s actually the easy part. The configuration in the user interface is the more difficult part. Plus then I have to write the iOS version interface and code to react to the settings.

So no exact timeline just yet.