I’m picking up that code to reuse it on the next App, which will be similar but this time, based on the National Soccer League(s) with the addition of one or two interesting features, I hope.
This post is focused on the strategy that I used for our App’s main interface and data updates.
Starting by the data updates, our App gets the data from the server, downloading three XML files, each one with:
- match results;
- best scorers.
For the user interface I’ve used some standard iPhone controls (mainly for buttons) but the main screen is almost filled with an UIWebView.
What that means?
That means that the mainly part of our App UI is done using standard HTML web pages. I had some problems to implement this “workflow”, but after achieving that, it allowed us to easily tune our UI, using standard web technologies: HTML + CSS.
The main pages/views are obtained via XSLT:
XML -> XSLT (with CSS) applied -> HTML
So, when the App updates data, it receives three XML files, the correspondent XML data for the screen that the user is seeing, is transformed applying a corresponding XSLT file and then the new HTML page is generated and presented on the UIWebView.
I know this method is not so fast as if I had only used iPhone controls from the UIKit Framework for the views. But the pages scroll and transitions are fluid, except on the first time the App creates and presents each view, which take maybe 2 or 3 seconds do appear.
That’s not perfect, but it was a nice trade-off which allowed us to cut some time (that would be used to learn to use those controls) on our App development and design.
Nevertheless, in the future maybe it’ll be easily to port it to Android OS or any other platform which supports web views.
I’d like to hear your opinions and suggestions about this scheme or better alternatives. Leave me a comment…