I have read many post indicating that we can't send sms on Missed Call, but i would like to know the reason behind that.
Also there was a app called "Agile reply" for iphone but i cant find that app in the app store actually.it seems that it has been removed from the app store
I would like to develop an app like sending sms on missed call / un answered call.that app needs to be posted on "App store".my app needs to run on iOS 4.0 and 5.0
Please share your view on developing app with this kind of functionality and its possibility
why this kind of app will be rejected.
The Agile Reply app didn't send texts automatically upon a missed or unanswered call -- it just allowed you to quickly compose a message to the last number that called.
If Apple have decided they're unhappy with this sort of app, that's the end of the story. They have their reason(s), and whatever you think of those reasons, they're the gatekeeper of the app store; their say is final. Of course it might be possible to develop something like this for jailbroken devices, but that's a different story.
As for the reason that Apple didn't like the Agile Reply app: the following two reasons seem plausible to me (but are also just educated guesses on my behalf):
1) The app accessed private APIs
2) Apple thought that the app didn't offer anything new or worthy: they might have reasoned that it is easy enough to go into the built-in phone app, select the last (missed) call, and compose a message to that number, without the need for a custom app
Related
knowing that the review process for apps seems to be rather rigid to some extend I would like to ask if there are any special requrements for an app that is targeted to work with certain Midi interfaces only. The particular reason I ask is that this app can not really be tested when not connected to such an interface. Thanks
There is no specific rule regarding this.
App Store Review Guidelines
To be on the safe side, describe this when submitting the app, there is a text field to add a message to the reviewers.
In the meanwhile I submitted my app and it got rejected in the first phase because I did not include a demo video. So after I created one and put it on YouTube, provided Apple with the link, everything went well.
So as a definite advice not to loose time until Apple comes back after a week or two to just tell you to provide a video - include it right from the beginning....
I saw a new app called Agile Reply which allows you to send a sms to the person whom just called you. I didn't buy the app but I don't understand how it would work since as far as I know you can't access the call log through the official iPhone SDK. So my main question is:
Are there new API's in the iPhone SDK which allow you to access the iPhone's Call log?
I know there are similar questions here and here however I didn't know if I should hijack those or start a new one.
Take a look at CoreTelephony. While it won't give you arbitrary access to call logs, you can get notifications of call transitions, which if you can keep at least in the suspended state, may be enough. I don't know how accurate Agile Reply is.
I found the solution here but it doesn't work for iOS5.
http://iosstuff.wordpress.com/2011/08/19/accessing-iphone-call-history/
I'm new to mac/iOS development. I'm thinking of to develop a UI less application by using existing Apps/Libraries.
I want to know whether following things will be possible to make or not, it will be great if someone provides me some insight.
Here are my questions:
Is it possible to show/hook additional buttons on existing contacts
-> contacts view (some additional buttons under FaceTime button)?
Is it possible to route some messages to SMS inbox? where the user
feels like he received/sent the real SMS?
In short: no.
In somewhat longer: iOS applications run in a sandbox that rather severely limits their ability to interact with the outside world. This is for the purpose of protecting the user's security and experience using the device. It MIGHT be possible to accomplish both of those things if you were running on a jailbroken device and using non-public APIS (though frankly I doubt you'd be able to add buttons to the existing contacts list by any means at all). But such an app couldn't be sold in Apple's app store.
I want to integrate the iPhone sms like chat bubbles in my application. But when I read more about it I found that this will not be approved by the app store. Is this true? Cant we use chat bubbles in the application?
Here are some links which describes this.
http://www.iphonestalk.com/iphone-app-store-submission-rejectedbecause-of-chat-bubbles-angry-developer-speaks-out-5836/
Thank you
The article is over a year old.
There are hundreds, if not thousands of apps in the app store using chat bubble images that look identical to those used in the SMS app.
Some of those apps I use, some of them I created. I've never had a rejection based on the chat bubbles.
Based on the link, it sounds like it. Although I would review the full app store review guidelines here (Note: requires you to sign in as an Apple developer). When you think about it, it makes sense though. Apple has spent a lot of time designing a unique interface and if they have, in fact, trademarked/patented that style of displaying a two-way chat, there's no way they're going to let you use it.
To be honest with you, I think it's likely more complicated than "yes you can use chat bubbles" or "no you cannot use chat bubbles." There are probably some fairly specific guidelines that define what Apple has trademarked/protected and what they haven't, hence the suggestion to make them less shiny. Long and short of it is, if you application looks exactly like the iPhone SMS application, I don't see it fairing well in the review process.
I've been waiting on an iPhone app to go through the app store approval process. It's been in the queue for about two weeks now.
Apple recently added something to the dev center about reachability, pointing developers to their sample app. In my app, I'm posting to a URL on my server using HTTP - but I'm not doing a reachability check first. If the user tries to submit the request, it will eventually time out and they will see an error.
What are the chances that Apple will fail this app? I'm wondering if I should just quickly implement reachability and "reject binary" myself, submitting a new version. Might save me a couple of days if I'm just going to get rejected anyway.
Implement reachability, if your app uses the web and when there is no connectivity the app doesnt say something along the lines that "this is not working because you have no internet access" then 95 percent it will be rejected by apple
Sounds like you answered your own question to me - not handling that case is a serious UX problem you should definitely fix.
If I were expecting to deal with a reasonable, smart approval process, I would do exactly that -- fix the app to match their new documents. It's a classy move, implying you'd be a good citizen.
You may want to rely on someone who's been through the iPhone app store, though, for an answer with the right amount of cynicism.