12.3: Apps that are simply web clippings, content aggregators, or a collection of links, may be rejected Does this means that I can't use the Customer HTML/URL plugin? Thanks and Regards, SKywalker

Keep your chin up, many folks have had the same email and now have dozens of live apps. Apple want you to use that lovely hardware and device capabilities in your apps, an app that could just as easily be a web app, html and the likes will likely - as you just experienced - get kicked back. Think of it as encouragement from Apple, not rejection. By all means use the custom HTML and URL plugins, I use them all the time without issue. But an app that is just copy that can be found on the web results in your post. Add some other menus that take you into these URLs. It's kind of old school now but maps, interactive menus, shake features all show off the device capabilities as opposed to just HTML. Hope some of the above makes sense buddy. Stick with it and may the force of BT be with you.

hi, MacApple thanks so much for your experience sharing...^_^ actually I want to build a APP of some industry, one page of this app is called "platform", in there, people can login in different websites of that industry to do business.. so in this vision, I used the custom URL with the address of each website, but was rejected by App Store as "web links collectors " So I decide to integrate the websites' API key and screte login in GUI into my app to make more like a native app rather than web app... Does you know how to do that? is there already a plugin on market can help me do that? Thanks and Regards, Skywalker

In my experience no two API keys are the same. Think of Buzztouch api, Flickr api both are implemented differently but essentially tie in to a backend service for validation. You are essentially using the key to identify what service you are calling. *bad explanation* It's like a token for tracking use etc. I'm sure you don't need me to explain that so moving on. Whatever API key you are using you are probably not the first so have a Google search and see what pops up. I'll bet if someone hasn't used it on here StackOverFlow will have a few snippets. Drop in a nice button menu or carousel menu to lead into the URL screens you are using. Hide the fact that it is just a series of links. Design around that principle. Make sense?

I have design it with beautiful image buttons around, it like a native app in appearance...

OK, so keep working on that. I hate to say it but hide the fact that it is just URL and HTML links. Pad it out, add in some maps, quizzes interactive features. OK, forget the quizzes and so on but make the app use the phone, use the hardware, use iOS cool features. Again, most of us have been there, heads down, move on and when it goes in and goes live it feels even better. Like beating the bully at the second time of asking.