Web Views and Wrap-Up

When considering the CRUD technique for managing data, developers tend to think about creating a single form / view to support Create, Read and Update. In the web world, this isn't necessarily a bad idea. (In fact, it can be very good.) When transitioning over to the mobile environment, there may be a tendency to think the same way. Specifically, if I've built a view for creating and editing data, then I should use the same view for displaying read-only data.

What these developers forget is that another option exists: Use the mobile device's built-in web browser view to display this data. The web view is a rich control that supports all sorts of formatting. Even better, it's possible to perform all of the necessary transforms on the server - this minimizes the amount of device-specific code that must be written.

In this article, I'll demonstrate how to display the details of a catch to a user by embedding the browser control into a view. I'll also touch on a multi-screen technique for capturing the details of a catch. (As you may recall, the details surrounding a catch can't be contained within a single view, so I'll demonstrate how to navigate between views.