More Mobile Software

Any news on progress to share dives with buddies?
It’s been requested for over 4 years now.
We need to be able to share (send) a specific dive to a buddy and have them upload it into their Dive Log.
The current Share functionality doesnt do that and is pretty useless

I’d imagine it wouldn’t be too hard to export selected dives to a DB file…..that is shared/sent to another user…who then imports them - just like the current experience for downloading from a dive computer. On import it could ask if you want to create the dive site info as you go…..

But there is no way to currently do this?
Very frustrating when one diver has all the info and others have to re-type it in.

Brilliant app otherwise

In fact Ive just looked at the export/import function in the latest version and *all* it needs to make this happen is the ability to *selectively* export…and then selectively import the DL format file.
Don’t understand why that functionality isn’t there right now?
Just being able to choose which dives to export…and then choose which ones to import….would facilitate dive log book sharing between users.
Why is the DL export/import an ‘all or nothing’ option?

Hi,

Yes, you are right ... "all" it needs is to support selectively importing (and exporting) dives. Unfortunately it is not quite the same as importing a dive from a dive computer. Because of the nature of databases (for example Buddies, dive sites, etc. are stored in a different table than a dive), it is a bit trickier than the obvious statement. This is definitely on our list to get done within Dive Log, but we have have not been able to allocate the resources to complete it just yet in the face of other priorities. I'll take your post as a reason to readjust our priorities and we will do our best to get something done.

If you happen to also have access to our Mac software (wither the paid DiveLogDT or the free DiveLogManager) it is possible to selectively import dives from an existing Dive Log database. So if you were to share your whole logbook your Buddy could import just the dives of interest (this will also pull across information like dive sites). There is also an option to export some items like dive sites to a format that can be imported by another copy of DiveLogDT/DiveLogManager.

I realize that this is a poor substitute for your use case, but maybe it can help until we can get similar functionality into Dive Log itself. I apologize that you have had to wait so long for this feature.

Cheers,
Greg

Thanks for the reply Greg.
I appreciate the challenge is dealing with different priority requests for functionality.
Perhaps an approach could be to take it in stages?

First iteration could be to add the function in a ‘simple’ import mode - ie it brings in all the info that doesnt need additional table creation logic - in the same way as it imports from a dive computer. That way it would at least import date, time, depth, temperature, profile etc……so it’s almost like importing from someone else’s dive computer (via the app)…….
that would be an improvement on what we have now …..next iteration could be that it imports/creates the location info (eg site etc)……and so on.

That would allow you to stagger the effort required?
Just a thought.
Cheers
Al.

Thanks Al,

I appreciate the ideas. We'll certainly see what we can do.

Cheers,

Greg

Hello,
is there an update for this feature?

Or is there at least a timeframe in which you can say that this feature will come?
Can we even assume that this will still come?

This function would be very important (to me).
It is very time-consuming to always enter the same information for each buddy individually and also the data from the dive computer must be imported again individually for each.

Hi,

Thank you for the additional expression of interest in this feature. As stated earlier in this thread, we do our best to add features based on a priority scheme and additional feedback about the desirability of a certain feature helps inform that priority. Note that bug fixes and adjusting to new versions of iOS are always first priority as that is something that you, as customer, have already paid for. We never promise new features as we can't guarantee we will have the resources to develop these features.

That said, we do work to add features that users want as quickly as we can and always appreciate learning more about specific use cases. I would be curious to know more about the scenario where you want to share a dive computer profile with another user. Obviously, as a matter of safety, each diver should be keeping track of their own depth and time (and if they are using a dive computer, have their own dive computer to accurately track their decompression profile). The resulting logbook entries are not that important as long as the diver is not using them for future dive planning, so if it is just used as a way to populate *some* data I guess I can understand that (although it seems like a low volume use case on the surface of it). I'd certainly appreciate learning about your use case and how sharing of specific dives helps meet your goals as it would help with designing the implementation of this feature.

One way that you can partly meet your need to share dive data today is to use the Synchronization->Export->Export DAN DL7 format option to share specific dives to iCloud or another configured service (like Dropbox) and then each user can import those dives using the Synchronization->Import->Import DAN DL7 format option. While this will not transfer all the details of the dive, it will transfer the basic data that you have mentioned (depth, time, profile).

There is a way to achieve sharing of full dives including location information using our Mac product DiveLogDT. DiveLogDT can import dive data from an existing Dive Log/DiveLogDT logbook into another logbook. This will transfer all the dive data along with dive site, city and country data for any chosen dives. You could export your logbook to iCloud and then import the dives of interest into each logbook for your buddies that have been synced with DiveLogDT and then sync the result back to that user's iPhone before repeating the process for an additional user.

I know this is not the answer you are looking for, but rest assured we are doing the best that we can with our available resources and we have not forgotten about this feature request.

Cheers,

Greg