Share Your Thoughts

Comments

  1. Jishnu R says

    Thanks for the post.
    It should be possible to support single page application in offline mode right? Let’s say the application is developed in Angular we cache the whole application using manifest file. The SPA should work without any need for network. With HTML storage, we should be able to store previously retrieved data and use this data to display when the application is running in offline mode. Is this correct?

    • Miguel Guardo says

      That is correct Jishnu,

      As long as you capture every single page the application needs to work offline – the first time the user accesses the app – you are good to go. The user will be able to run the application when offline.

      To cache data, we are using IndexedDB ourselves but you can also use localStorage.

      In this post I am providing a very basic example – without the IndexedDB component – but the BeeBole mobile application is just that: A Single Page Application that works offline

      Cheers!
      Miguel

  2. Michel says

    Maybe not the right place to ask.
    But im wondering how do you navigate cms pages.

    lets say you have a blog and products.
    The urls are most of the time not defined by a natural patterns.

    so how does a pwa routing send the urls to the right components.
    – product
    – news
    – content

  3. Miguel Guardo says

    Hi Michael,

    I would say the standard PWA behavior is to cache all static pages that your application need to run offline. If your pages are dynamically created, you can always add some logic in your Service Worker to cache pages as they are navigated by the user. This way, user will be able to at least get access to those pages in case the connection is lost.

    Kind regards,
    Miguel

  4. Leslie says

    The question was asked:
    “How do I make sure my Chrome console uses the last version of the files when developing and testing on localhost?”

    The answer was to remove cache and reload. I had the same problem with my github site. Doing so all the time was cumbersome and — left me confused as to why the latest code wasn’t ALWAYS loading up immediately. While developing, an older version of my code was kept showing up. Then I discovered my problem. I needed to remove the lingering COOKIES. Go to your secured site, click on the lock icon, and delete them cookies!

    • Miguel Guardo says

      Hi Leslie,

      Thanks for your comment. Deleting the cookies will work but will force you to login again if you are using an authorized app, which is our case. The quickest way (for me) to make sure the last pages are taken into account is to use the Application >> Clear storage option from the Chrome console menu. Then make sure that you select the box to clean up the cache storage and click on ‘Clear site data’

Leave a Reply

Your email address will not be published. Required fields are marked *

Know where your time goes
BeeBole Timesheet is helping more than 1000 companies in the world to optimize time and resources.
  1. Flexible time-tracking
  2. Business reports
  3. 1-1 support
  4. API and integrations
  5. Multilingual
  6. Secure
Send this to a friend