@RHo I was trying to look in more detail and somehow "closed" this mock. I don't know what that means - feel free to undo.
I really like how slick the fallback to the offline pack is. As we're going forward, we may want to consider making it easier/more intuitive for people to access offline content when they're online (for data savings), such as moving access for both Compilations and Saved Pages into a closer workflow.
@atgo - cool I am not sure what closing the mock mean but seems it's still visible to everyone so think it's fine as is.
Re: making it easier to access offline content for data savings, definitely something we're looking to do – adding a data-savings preference to use offline packs even when you are online (T166596) is slated for v1, and looking to include an explicit offline mode (T164756) in v2.
Re: making it easier to access offline content for data savings, definitely something we're looking to do – adding a data-savings preference to use offline packs even when you are online (T166596) is slated for v1
Hope you distinguish the pages that are loaded from a compilation well!
N.B.: I suppose a toast wouldn't suffice in this case as the article is being loaded from a compilation even when an user is online. So, when a user leaves the app with an offline version of a page and comes back after some time he wouldn't be shown a toast in all cases. He might not be able to identify if it's an online version from wikipedia (or) an offline version loaded from a compilation (aka article pack).
hi @Kaartic - yes, we are using more up to date mocks linked on relevant tickets in development, this particular mock was used early on to outline the high-level workflow of the feature.
Re: your question/comment about distinguishing pages that are from an offline compilation, we do so both by having the toast notification when an article initials loads, as well as noting the version date and which compilation it is from in the article's footer, as captured in this task T166652