You could cache bookmark data (at least some of it) locally in isolated storage. This is easy to do with DevForce and is demonstrated in Model Explorer and Prism Explorer.
The challenge is to know when the user has bookmarked the current page. It may be difficult to get that information from the browser. Of course you could offer a button to press to capture the proper deep link. Or you could just save locally a rolling list of the most recently seen customer details; when the app launches with a link, you can compare it (compare the customer details id component of the URL query string) to your local store of customer details and, if you're lucky, you can present the data immediately.
Whether I had a hit or a miss, I would immediately launch an async query to retrieve the most current version of the customer detail. I might also provide a UI cue that the data presently on screen are old (and maybe say how old).
None of this is any help if you intend to send the link to someone else; that someone is unlikely to have the targeted customer detail in cache.
Hope this inspires you to great things.
|