Is there any way (even a single way) to change ringer mode of iPhone (silent or vibrate) through our own app (don't worry about the app store). Kindly share with all if you know any as many developers want to explore this side.
Regards.
I don't think so, Apple doesn't want devs messing with the basic phone functionality.
Not possible. Private API is illegal to access. Recommended not to make these kind of apps.
Related
I'm close to publishing an iPhone game on the AppStore and I'm wondering what would be the best way to publish a multilingual game...
Should I use the iPhone language settings to load the language accordingly?
Publish multiple versions of the same game but in different languages?
Put a setting on the game to change languages (or would users prefer not to use this one...) ?
Any ideas, recommendations, or best practices would be greatly appreciated.
One app. Period.
Always use the user's current locale, and make a reasonable assumption for default in case you lack localizations users may be using. I've seen most commonly English be used as the default. Myself, I wouldn't even supply an override; the user has the device in their preferred localization already.
I would definitely include all languages in a single app. You could set the default language to the language that the user has enabled on his phone and add an additional option in your app's settings.
I will be publishing an App in a few days. Initially I don't want to add advertisements, but can change my mind anytime, so I've thought this. Add a WebView to application and set its image to a dynamic web content. If no ads; I will display a simple logo, but when ads are available, replace the content with them. So there will be no modification to iPhone compiled binary.
Do you think it is allowed by Apple, and a good approach?
If you follow that approach, you will need to at least explain to Apple when you submit the app for review that ads may be enabled via a webservice.
Apple won't like it if you don't tell them that you might modify the apps feature set or behaviour after its approval.
You should be OK as long as you tell them about it.
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?
I'm not all that familiar with Apple's iPhone development system, but I'm trying to figure out if theres a way for developers who create custom iPhone apps to update their apps on a mass scale. For example, would a company who publishes hundreds of apps have to resubmit every app they've made manually if they find a minor bug that affects all their apps (assuming they have used a template)? Or is it possible to somehow use or build a custom program that can make this process easier, by automatically generating or updating apps? I don't believe Apple has an API or anything, but it just seems like it would be a nightmare for these developers to fix bugs, and thought maybe I was missing something.
Thanks in advance for your help!
Apple provides no way to automate this. In theory you could write a program to simulate a browser to login and upload new binaries for you, but I'm not sure Apple would like that very much, and it would be a lot of work.
In addition, one might argue that if the apps are similar enough to warrant this automation, it should probably be one app instead of many. But that may be an over generalization without knowing your use case.
There's the Application Loader
http://itunesconnect.apple.com/apploader/ApplicationLoader_1.2.dmg
(requires login)
It doesn't do bulk uploads, but it does provide a maybe more accessible interface.
Isn't there that separate application that you can use to talk to iTunesConnect? (Though I still don't think it's possible to do mass updates.)
Can anyone tell me the best way to go about making an iPhone application support multiple languages? I am going to put separate versions for each language in the App Store, but what is the best way to represent this in Xcode?
Putting a separate app in the store for each language is NOT the way to go. The iPhone SDK handles multiple languages with grace, and you only need to have a single app with all the various translations. The iPhone's locale setting will direct your app as to which language to use.
A good place to start is here.
I haven't done iPhone dev yet, but "normal" Cocoa apps use ".lproj" strings files for different languages. See the docs about those, that should help. Good luck.