Thought Processes from a Silverlight OOB App Dev
As I’ve been working on a major Silverlight project recently, I was talking with some app devs, who kindly reminded me that I can’t account for every click and every end user behavior. But I’m determined to user-proof my app as much as I can. I want the user experience to be as enjoyable as possible. (Yes, a UX tie… this is a Sarah on User eXperience – SUX – post in disguise.) These are just some of the considerations that I’ve been thinking about wh
ile working on my out-of-browser (OOB) Silverlight app.
How do I handle OOB behavior when the app is in-browser?
Silverlight in the browser really gets cranky when it sees those Application.MainWindow calls. So I’ve had to make sure that OOB-specific calls are hidden away well enough that the in-browser side doesn’t see them. Of course, there’s the Application.IsRunningOutsideOfBrowser Property – very handy for checking if the app is running OOB first before making those calls.
Of course, if the app is starting in the browser, some other things to consider include:
- An in-browser interface. What’s the app going to do while it’s in-browser?
- How will the end user install the app? Do you have them right-click on the app and install from the Install menu or do you add functionality to the in-browser app and use the Application.Install Method?