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

General discussions of "offline"-like access strategies #72

Open
fititnt opened this issue Apr 14, 2020 · 5 comments
Open

General discussions of "offline"-like access strategies #72

fititnt opened this issue Apr 14, 2020 · 5 comments

Comments

@fititnt
Copy link
Contributor

fititnt commented Apr 14, 2020

Quick question: considering the target audience of HXLDash, the potential of have "offline"-like access is desirable? (In practice, means someone who already accessed some page, if internet goes down, it would try the local copy of a dashboard instead of go offline)

This issue is not necessary about how to implement, but if the subject is desirable, so people may contribute later. If yes, (or if no) we can just close this issue.


Some of my previous search on HXL tools

The HXLStandard/hxl-hashtag-chooser at the commit HXLStandard/hxl-hashtag-chooser@d948bac tried with AppCache [1] that is easier to implement at coding level, but have some caverats (one notable issue is that the appcache manifest needs to be served with very specific mime type, so it needs some support near server level, so using GitHub pages fails). Another approach (that I personally did not tried yet, but seems feasible and is the replacement of AppCache) is would be Service Workers [2].

If "offline"-like access is desirable, other issues may be added on the future. In fact, maybe would be easier to implement at first on the HXLStandard/hxl-hashtag-choose (since does not have dynamic content) and later try something on hxldash or do on the hxldash in smaller increments.

1: https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache
2: https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers

@SimonbJohnson
Copy link
Owner

This is a really interesting suggestion. I will see how this feature is received by some of our current users.

@fititnt
Copy link
Contributor Author

fititnt commented Apr 15, 2020

Sounds like a plan.

@fititnt fititnt closed this as completed Apr 15, 2020
@SimonbJohnson
Copy link
Owner

Let keep this open for now in case it sparks more discussion!

@SimonbJohnson SimonbJohnson reopened this Apr 16, 2020
@fititnt fititnt changed the title Desirability of "offline"-like access General discussions of "offline"-like access strategies Apr 16, 2020
@fititnt
Copy link
Contributor Author

fititnt commented Apr 16, 2020

Ok. I was planning to break in several smaller issues, but we can keep a single big one. And trust me, this can go very deep.

Changed the title from Desirability of "offline"-like access to General discussions of "offline"-like access strategies

@fititnt
Copy link
Contributor Author

fititnt commented Apr 16, 2020

refs:


Potential bug of "offline"-like access strategies when using Free Basics internet (not confirmed)

User case: Some users may have a mix of both "full internet access" and "free basics" access. They sometimes may pay for some hours or for a day to access most content they can, but later want to revisit.

Potential undesired behaviors:

  1. They can (without put phones on offline mode) get access to the cached version
  2. If they re-access the page (but first time where on free basics like internet) the browser will invalidate the cached version

Potential ways to test:

  1. Maybe we create some simpler html page with example content and ask people to test how the behavior occurs.
  • I have contact with a peer from Angola and other from Mozambique (not sure what phone company their are using now); I could try ask more people to test
  • Actually I'm not 100% sure about the limited access companies on Brazil may give to the users (Brazil does not have Free Basics, but the companies still do some packages with only WhatsApp/Facebook access)

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

2 participants