Offline behaviour

purple native apps still work when your device isn't connected to the internet however, there are some limits to what you can do without an internet connection this article explains offline behaviour and how you can define an offline view to let your users know that they are currently not online while using your app offline behaviour in purple apps purple native apps still work even if your users' device isn't connected to the internet however, there are some limits on what you can do without internet connectivity here are the basics first time usage of the app the first time using the app, the user needs to be connected to the internet once something in the app has been viewed, it's cached so it can be viewed again without an internet connection sign in/out when signing in or signing out, the cache is cleared, and content will disappear or queries will not be resolved this happens because some options within the app change depending on the login status when trying to sign in or sign out in offline mode, it's likely that the user won't be able to see views while staying offline search some searches won't work offline unless you've already looked at them online at least once, even if you set them to only show things you've saved downloaded content define offline views to ensure consistent usability while being offline, we recommend creating a view that displays all content that is completely or depending on your desired behavior partially available for offline usage to ensure the app gracefully starts in offline mode, ensure there is no data from online sources needed upon startup implement proper fallbacks here, otherwise you might end in an undefined state to ensure your users can easily find this view, you can trigger a message if the device is online and link directly to the aforementioned view downloaded content view this view may show content you've explicitly saved and content you've viewed online downloaded content behaviour content that was not downloaded explicitly is available only up to the point where it was consumed before, e g an issue will only be displayed up to the page that it was read before we do not explicitly download thumbnails , so they will only appear if the user has had a look at the downloads page before going offline here's how to do that 1\) in experience builder > views json, you can create a view to display downloaded content, including partially downloaded elements views json in experience builder note that the actual value of the emptymessage is controlled via messages json for further details on that, see messages json static texts docid 2l6zp7jyafzv xnfoy8u0 offline notification and link 2\) you can now create a message that will be triggered if the device is offline to ensure maintainability, this should be done in two steps a) creation of a view with the desired message and behaviour not depicted, but possible is to add further tracking parameters to that view as well (see configure views for tracking docid fg4ut3gcm6zfwalv ocb for details) you are free to add css accordingly to style that part to your need b) inserting that view into any other view where you want to display the message with this approach, you can make significant changes to the message without manually altering many views you also get the freedom to integrate other elements that you trigger on specific conditions