5. Review and go around in circles - mobile is all about the APIs silly!
AjayChebbi devWorks 270004DG8B Visits (1285)
So, why all this talk of lean and agile and all that? the whole idea is to be able to get incremental feedback - and have the ability to quickly react to the feedback. That's pretty much there is to it.
So we set out to build the one screen - which would display the steps in a test script. And as I mentioned we started using JQuery to build it. It was available by default, seemed easy enough and the Intern has very little trouble picking it up... and above all a lot of great help is available on Google. Oh wait - google does not itself "provide" the support. or does it. Wait I am confused... need to go check this one more time...
In the meanwhile the effort began. Within one week we had a bare bones screen - the login screen. authentication and certificate handling from a hybrid app is a pain. My boss came around and said what's up! and we said meekly - we are having trouble authenticating to the freezin server... sir.. please... thank you.. talk to you again... He had a look on his face "why are these guys mumbling.. people login all the time.
Yup. Time to switch gears. Don't underestimate the complexity of securely logging in to a server - but that has very little sweet appeal. and people don't buy your app because you can login.. there are a lot of apps that can login.. duh.. So we said - lets assume we procure some pixie dust and get over the login. what do we do next - do we know? I came up with a plan. Look there is a sequence of steps needed to get the app running. Lets not worry about that yet. what is the most important thing about the app that some one will make the buying decision? Of course besides login.Yup. Right. (Im thinking of dedicating a future episode only on login)
The most important thing is the abilty to show the test steps which contain a description and expected result etc. So we used Firefox Poster to get the return XML of the test result. Hardcoded it as a string and parse and build a UI o top of it! Smoke and mirrors? well not exactly. We know we have the API to get it, and we need to parse it and display it any ways.. we just had not connected the dots yet. Did a review again with some folks.. and they started to get it! Yay!
I would not bother re-writing the APIS to JSON if they are returning a perfectly usable XML. You can always parse them using something like the dojo