For HTML5 offline applications with ASP.NET see link and link.
There are several alternatives for autonomous functions:
01 . If you need to store small amounts of data in a standalone application, and security is not a big concern, you can use the HTML5 web storage ( link , link , link ,, and see CanIUse to find out the version of browser support).
The main disadvantages are the lack of security based on the key value (without complex structures), and there is a large storage size limit (5 MB for most browsers).
02 . If you need more data, you can look at the IndexDB link (, link , and CanIUse ) or Web Sql ( link , link , link and CanIUse for browser support).
The main disadvantages of web SQL are that Firefox is not supported by IE. In addition, it is deprecated by the W3C.
IndexDB is nice ( link ), but ios doesn't seem to support it anyway (see canIUse).
For approaches 1 and 2, you can create a responsive design or a dedicated mobile website in your ASP.NET application ( link ).
03 - (great flexibility requires a lot of effort) Implementing a web service in an ASP.NET application and a mobile application using the concepts of "Randomly connected applications" (more: link )
ASP.NET Web Application => For a web application, expose a web service with services related to stand-alone functionality.
Mobile application => Implement your own mobile application (for example, create an application for Android and iphone) with a database for the application. Then you create a standalone function in a mobile application that will use its own database to read and write (locally) data that should be available offline.
Then you implement the silent synchronization mechanism in a mobile application that relies on the Internet (for example, a repeating stream) that will look for updates by accessing the ASP.NET application through a web service. This synchronization mechanism will send data that has been saved locally and restore data from the web service, which may be useful for offline work.
Hope this helps.