feature: improve location sharing

• share position to different conversations at the same time
• Be able to stop sharing positions with the current conversation only
• UI improvements to know who is sharing and who you are sharing to
• Be able to unpin map
• Handle multiple maps at the same time

assigned to @nvengeon

added sprintto review label

mentioned in commit 933cce8c

• Switch account and go back -> sharing icon on avatars are gone
• Improve design
• Clean positionManager (last method)
• unpin window
• Zoom issue

added sprintdone label and removed sprintto review label

changed the description

mentioned in commit 995bd420

changed the description

changed the description

23061: feature: improve location sharing | https://review.jami.net/c/jami-client-qt/+/23061 23329: Feature: unpin location sharing map | https://review.jami.net/c/jami-client-qt/+/23329

added sprintin progress label and removed sprintdone label

added ui/ux label

More Improvement Ideas:

• Direction, speed
• Valid auto-share time (example: work hours, or 'leaving work' time for wife)
• Always Share with Contact
• Temporary share with contact
• Share during calendar event
• Set meetup location (pin location, "John has set a meetup location" notification fire)
• Share location when bluetooth device is discovered ("Connecting to car shares location with wife/kids automatically" - Sharing location due to car connection")
• Leave location notification ("share my location when I leave this area -> Wife")
• Share location due to 'run' or 'bike' app ("John has started a run")

Direction, speed

What would be the most bsttery-friendly way to do this? I'm thinking using accelerometer data compared against two GPS pings/locations (current and previous) could do this. But, I have no expertise here. I'd also recommend adding a "~" next to the speed value, so that users understand that the numbers are very much approximate and not at all exact (unless we have a way of ensuring accuracy).

For sure, it could be exposed from the abstracted location in android and you could ask the user how often to update? The speed and direction could be based on 3 prior locations or something.

I know on android the GPS is only powered on if a precise location is requested and there isn't enough existing data to get a exact fix. For instance, AGPS from towers can provide the fix most of the time.

Cool. Seems like there's a lot of potential for neat features in the future with this. At least this one seems possibly easy to implement. Not sure about the others.

removed sprintin progress label

closed