i am developing a ebook reader app for iPad and i am facing a issue related to the design aspects of the bookshelf. I am posting a sample photo of my bookshelf here. I want the book shelf to have a horizontal navigation similar to that of the iBooks. Will this come under violation of Apple's HIG?? Will they consider this design to be a imitation of their iBooks design and reject it?? I'm worried...
Sadly they are not consistent about rejection. Good news they are more keen on their logos and device picture, so you can't use an iPhone/iPod in your app as picture for explain controls but sometimes you see apps like this. I am not developer myself but friends of mine and blogs about the topic says this. Thats why I didn't pay $99 for being a developer.
Your app resemble to Apple's app but in real life book shelves are resemble to each other, so we can call them the same. Bad thing: only by submitting it you will know they approve it or not...
Important thing, to kill all bug before this. If they approve it with the bug (that can happen), and then you want to update it, maybe they reject the updated version.
Related
I've created a web application using asp.net. I customized it form mobile(jQuery Mobile) .
I created an iphone application that has a web view that shows the website.
Is this will be applied by Apple to publish this application???
Regards,
Moayyad
If the only purpose of the app is showing the webview with the website, and it does absolutely nothing else, then it will most likely be rejected. However, if showing the website is just a small part of its functionality, and it does some other useful things as well, then using a webview for displaying your own website is OK, as far as I know.
Note, however, that I/we can only make assumptions and guesses. Nobody except Apple knows what exactly will happen to your app - there are numerous cases when an app was rejected for a feature which another approved app had, so there are inconsistencies in the AppStore approval policy of Apple. Don't expect anything.
I don't think so. They prefer use of HTML5 in webapp. Try to review the Apple guidelines for building web app.
I am planning to develop a free app. Which could be useful for many people. So, I am planning to put a donate button inside my app. So if any people finds it useful, they will donate for development.
Is it good if we implement in app purchase to achieve this functionality.
I am not sure is this possible. Please correct me if this question is wrong and I will remove it.
Thank you in advance.
Try to search. There are multiple questions on how to handle donations.
You have to look for App Store Review Guidelines
https://developer.apple.com/appstore/resources/approval/guidelines.html
See 11.2 - 11.4 and judge if donation to non-charities (Charities covered in 12) are allowed:
I would say no. This is virtual goods not consumed inside the App.
To work around it, let people pay for a different background color or some minor functionality such that you can stay in compliance. Or make 2 versions, telling them to support development by buying the other version (you can link to it). The 2 versions could probably be the same or almost the same.
We are wanting to modify our app and create a way to allow mobile users to shop at our store. I know apple get's 30% of the revenue from the App sales itself, but do they get 30% of the sales made through our app? If so, Would we be better off making an ecommerce website designed for mobile users and then making a link to that page from our app? If we do that, would Apple still get a portion of our revenue? Thanks for the help.
Yep, same 70/30 finding a link now...
http://www.businessinsider.com/apple-lets-iphone-app-developers-sell-stuff-in-free-apps-2009-10
Now this is just using apple's in-app APIs. If you just have people buy stuff through your store from the app but bypassing Apple they get no cut.
EDIT::
Actually here is a better answer:
http://www.iphonedevsdk.com/forum/business-legal-app-store/60030-will-apple-take-commission-app-sells-goods-within-app.html
Yeah, they're not keen on you selling things out with their store because yes, they do want your 30%. I think newspapers and magazines are currently battling with them over some sort of subscription that works similar to this but for now you're unlikely to get this through the net.
.
Amazon and a few others get around this by having a buy button that launches their website in Mobile Safari, where you can sell items without any Apple involvement.
As far as I know, Apple takes 30% of the price of the app in the store, not the revenue generated through it. How could they keep track of this revenue?
A client do not want to consider MonoTouch for a new project.
MonoTouch.info has a long list of apps, but I have not found any on the caliber that can convince a client too choose a technology. The client has seen the list, and actually use the bland screenshots as an argument against MonoTouch.
Where can I find examples of applications useful as motivation. High profile apps created using MonoTouch, the apps you call home about. The apps that made it to the top 25 lists in their category.?
I responded on Twitter but thought I'd reply properly here;
The first app I will mention is iCircuit - http://icircuitapp.com/ - this application is featured on the Apple website here - http://www.apple.com/ipad/business/apps/index.html#workflow-icircuit - and is a pretty good seller.
Diggify is a Digg application which hit the top #8 sold application in Canada apparently - http://www.intomobile.com/apps/diggify/359756952/
An application that I built myself (it's a little old now admittedly) but I do think that it looks rather nice - http://bit.ly/gfxmasappstore :)
London Bike App is another nice looking application - http://www.londonbikeapp.com/
Update: Wow, this is an old question, there's a whole bunch of great apps using MonoTouch at http://xamarin.com/apps
Hope this helps,
ChrisNTR
I know of a couple apps that were built using Monotouch and sold very well but due to the uncertainly surrounding the terms when MT first came out and later the 3.3.1 mess the devs didn't make a big fuss out of it. I suspect they aren't the only ones not publicizing what technology they used to make their app.
If your client is using a handful of screenshots on a website as the reason to rule out using Monotouch then you might want to rethink your pitch. Whether or not an app has been developed in native Objective-C or C# via Monotouch makes no difference on the overall design or appearance because both rely on the CocoaTouch framework for UI. Being able to deliver an app that meets your client's idea of what makes a great app has nothing to do with the language you use and has everything to do with your ability to translate the essence of their ideas into a solid design and UX. Sell that, not the framework.
I found this article to be helpful when I'm trying to explain to others why I use Monotouch over native objective-c.
"Why we chose MonoTouch to write the Diggify iPhone app"
This just saves time.
Since I already have a web applciation.
I can just stick it inside a webview.
The question is: Does it turn off many users? How many users will be disgusted that the entire iPhone app is written in WebView?
I think it's pretty safe to say that most iPhone users are expecting apps to use the power of the iPhone, not just be a portal to a mobile website.
Think about facebook mobile compared to iPhone facebook app. If you're an iPhone user, I'm assuming you'd much rather use the app than a mobile version of the site (or mobile version of the site contained in a WebView in a an app).
That being said, depending on your app, if the mobile version of your app is highly usable, it could be okay...
Just my thoughts...
John Gruber on Daring Fireball just wrote about this today.
From a usability perspective, native apps usually feel better. They may also be more responsive and handle large amounts of data more gracefully. I have a few so-called "apps" on my devices which are just glorified Web apps, and they don't necessarily scream quality.
If you've already done your app, then just ship it. But keep your mind open to feedback from your users.
The answer is almost certainly "no". People care far more about the usability and experience of interacting with your application than what API-supplied widget you use to render it.
I read Apple has begun removing apps that are like this. Well technically, they remove apps they think could be easily implemented as a webapp instead. Yours obviously qualifies ;)
Source: http://techcrunch.com/2010/03/07/apple-cookie-cutter-apps/
EDIT: Apple seems to not mind, according to the Human Interface Guidelines:
If you have a webpage or web application, you might choose to use a web view to implement a simple iPhone application that provides a wrapper for it.
Of course, Apple has a tendency to contradict themselves. ;)
Apple human interface guidelines says this isn't even allowed. I forget where it comes from, but somewhere in the guideline it says apps that are only web views are not allowed. I'm about 95% sure I've seen this. Can anyone confirm?