Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use less bandwidth—data-saver mode #265

Open
PattaFeuFeu opened this issue Feb 12, 2018 · 7 comments
Open

Use less bandwidth—data-saver mode #265

PattaFeuFeu opened this issue Feb 12, 2018 · 7 comments
Milestone

Comments

@PattaFeuFeu
Copy link
Collaborator

Mobile reception and mobile network speeds are getting better and better, but there are still quite a few places, especially in rural areas, where one doesn’t have the reception necessary to get fast response times within the app.

Thus, I’d like to propose a data-saver mode. Ideas on how that might be established include:

  • Use only cached images, don’t download new ones—unless user tapped on image if they absolutely want to download the image
  • Reduce request data
    • Even higher zoom level necessary to have the app download hosts
    • Only download messages if user swiped to refresh, not automatically
  • Map caching? (Not sure if this is possible with either in-app Google Maps or OSM (Add option to choose between Google Maps and OSM/OCM #264)
@saemy saemy added this to the 2.0.0 milestone Feb 12, 2018
@PattaFeuFeu
Copy link
Collaborator Author

Regarding map caching: I’ll check this StackOverflow post and the linked answers.

@dericke
Copy link

dericke commented Aug 22, 2018

Would the planned inclusion of OSM use raster tiles or vector tiles? The latter would reduce bandwidth considerably and could be cached on-device.

@PattaFeuFeu
Copy link
Collaborator Author

@dericke Excellent question!

OSMdroid, which we are planning on using for the OSM integration, currently doesn’t support vector maps, unfortunately.

osmdroid/osmdroid#246

@dericke
Copy link

dericke commented Aug 23, 2018

Ah, that's too bad. If you were starting from scratch, I would suggest that you use the open-source Mapbox Android library instead of OSMdroid, but I'm guessing there has already been work done towards OSMdroid integration. If that's the case, should I make a new issue to support vector tiles further into the future?

@PattaFeuFeu
Copy link
Collaborator Author

Vector tiles using OSMdroid or using Mapbox?

I don’t know how much time @saemy put into supporting OSMdroid; but we could have a look at vector tiles at some point. Supporting the maps downloaded from http://www.openandromaps.org/ would be another great addition.

@sgelb
Copy link
Collaborator

sgelb commented Sep 2, 2018

I don't know of online vector map sources that are suitable for this project. Mapbox is really great and I use them in another project of mine, but the Android SDK has a limit on free map downloads, see their pricing.

Offline maps would be really great, I opened another issue for this: #296.

@dericke
Copy link

dericke commented Sep 20, 2018

There's also maptiler.com as a potential vector tile source. I've never used them before, however.

Another non-profit organization that I volunteer for has been trialling Mapbox, and they may have special plans for registered non-profits. Someone would have to contact their sales team to learn more: https://www.mapbox.com/help/account-faq/#does-mapbox-offer-a-non-profit-or-educational-discount

saemy added a commit that referenced this issue Jan 14, 2019
Prevents any images from being loaded from the web. More might follow in
the future.
Also, switches to Glide as the image loading and caching library.

Updates: #265
saemy added a commit that referenced this issue Mar 27, 2019
Prevents any images from being loaded from the web. More might follow in
the future.
Also, switches to Glide as the image loading and caching library.

Updates: #265
Closes: #319
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants