{"id":144,"date":"2011-02-28T00:54:05","date_gmt":"2011-02-28T00:54:05","guid":{"rendered":"http:\/\/xphone.pt\/devnotes\/?p=144"},"modified":"2011-02-28T01:42:35","modified_gmt":"2011-02-28T01:42:35","slug":"json-vs-xml-data-size-parsing-and-display-speed","status":"publish","type":"post","link":"http:\/\/xphone.pt\/devnotes\/2011\/02\/json-vs-xml-data-size-parsing-and-display-speed\/","title":{"rendered":"JSON vs XML – Data Size, Parsing and Display Speed"},"content":{"rendered":"

In my previous post “App Interface and Data Update with UIWebViews, XML, XSLT and HTML<\/a>“, I’ve written a little bit about how I have used XML to dynamically update and display our App’s data.<\/p>\n

Following that, now that I’m preparing a new similar App, I’ve read lots of stuff about JSON and about JSON vs XML on the web, which is making me to consider the change of XML by JSON.<\/p>\n

Many people argues that JSON is better than XML but that’s not clear and it seems that it depends a lot in what we need to do! Well, I know that’s not something new, it’s what happens most of the times when we’ve to choose some technology against other(s).<\/p>\n

But I want to choose the “best” for my case, since I have plans to port this new App at least to Android OS and maybe to Windows Phone 7. And if that choice can reduce my total work in those platforms, it’ll be an important choice.<\/p>\n

In general what I’ve seen is that XML is largely supported in all common browsers and in those mobile platforms. JSON is relatively new, however it’s becoming supported almost everywhere but mostly without native parsers.<\/p>\n

That’s the case with iOS and WebKit (Safari’s engine). So I decided to do some previous experiments…<\/p>\n

Since this article is growing a little more than I preview, I’ll publish the results of my tests in the following posts:<\/p>\n