You have to also "simply" embed a download/update mechanism, "simply" test various restore scenarios (Consumable vs non-consumable receipts), "simply" make sure

You have to also "simply" embed a download/update mechanism, "simply" test various restore scenarios (Consumable vs non-consumable receipts), "simply" make sure it works in various orientations, and "simply" modify the way the entire organization works to suit Apple. The content is also different, taking a bunch of webdevs and telling them make this work on iOS does not result in compelling content layout, design, or navigation. There are subtleties in pinch&zoom, dragging, etc. that most webdevs have not had the pleasure? of dealing with. On top of that, UIWebView bridging js+objc is a PITA for iOS, and its a major problem for android where the 2 solutions are not even close to similar. So there is little code reuse between the viewers, and the content itself must be slightly different for the 2 platforms.