You asked earlier if you should be using PhoneGap. Such apps don't offer anything more than the user can do themselves by saving an icon for a website on their home screen. They are quite clear about this, and so there's no surprise that the app was rejected. Apple won't accept any app that is nothing more than a WebView pointing at a website. I might suggest picking something that is easier to produce than this for a first app. And, then, even though the material was already existing, it took several months of effort by several people to massage it into a suitable and desirable form, with many design and content changes along the way, based on feedback from the stakeholders.įrankly, few individuals would be able to afford the cost or time of producing something like this on their own. In both cases, the app is based on an already-existing printed guide, and the material was produced with the cooperation of government agencies and tourism councils, those who produced the printed guide, etc. which seems to be about the size these usually wind-up. It takes quite an effort and many individuals in different roles to produce a 200-page tourism app. I've worked on two, similar, travel/tourism-related apps recently (I'm currently working on something unrelated to tourism), and my technical role was only a small part of it. If that's the case, you picked a tough category. It sounds like you are doing this on your own. There are thousands of apps in the App Store that use jQuery Mobile. I don't think the use of jQuery Mobile is an issue. ![]() I think this has drifted off of the topic of jQuery Mobile, so I'll offer some closing suggestions. Not sure how much effort it would take to fully integrate Leaflet with JQM. It does use Leaflet, but uses data-rel="external" for the map page. I've contributed to another similar kind of project (for a South American city) that is not yet released. It's not a good solution, though, if the app needs to be able to map any place, rather than just within a region. Leaflet is a good alternative for apps that target a region, because then you can just store the map tiles in the device and don't need online access. Were I to do it again, though, I would likely use Leaflet for the map and store the tiles offline. Version 1.1 has been submitted (added a new trail, some minor fixes.) It uses PhoneGap, JQM 1.2,, -transitions, jquery.ui-maps, some custom tweaks. If most/all of your content is on a website, that won't fly with Apple. Maybe this will give you some idea of what is expected: (As well as significant development work.) It was accepted on first submission. Here's a recently-released app that I prepped for the App Store. They didn't say they rejected it because it uses a WebView. If your user interface is complex or less than very good it may be rejected ![]() in my app there are makers and it is look very good in my iphone and also it was touchable vsvs but they rejected.Why there are web view if they rejected web view based application?And i think maybe they rejected because it uses google map.Are there any google map alternative in IOS?īinary Rejected 2.12: Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be rejected 3.3: Apps with descriptions not relevant to the application content and functionality will be rejected 10.6: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. I developed jquery mobile map application and then i called this URL with IOS web view.And also used some other IOS features such as network connection control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |