I am presently developing an iOS application and also have arrived at the stage where I have to implement a server after sales to be able to offer the core functionality. Basically, the application handles text strings that should be submitted to some server. After finding the strings, I want the server to do some tasks by using it after which send caused by the duties (also string-based) to the apple iphone application.

I've zero server experience and am necessity of some advisement regarding where I ought to start with this. To be able to avoid financial risk, I'm trying to prevent devoted hosting at initial launch, therefore i wondered if at-home server hosting could be whatsoever feasible for the launch after which, when the server-side component was created properly, simply transfer the program to some more permanent devoted solution when the app's usage warranted. (Sorry in the event that last bit made no sense, I'll just namedrop XML and Ip to really make it appear like I understand what I am speaking about.)

I've done some investigation and I've discovered Amazon . com S3 to become a popular apple iphone application server solution because of its integration using the also popular wrapper, ASIHTTPRequest. This appears to become a more permanent hosting solution, however. Meanwhile, for local application testing on the more compact scale, an amount the suggested server platform be? Something like ubuntu with Light installed? If that's the case, would the scripts developed about the local platform (I am presuming in PHP) be directly transferrable to some bigger-scale server typically?

Thanks, and sorry for that most likely technically illiterate inquiry into servers. As you can tell, I am a new comer to this facet of development.

-Harrold K

I'd opt for hosting that is shared: http://webfaction.com or http://linode.com. It's unlikely that you are likely to have a lot traffic that the shared host won't have the ability to tolerate it. I operate a couple of high traffic applications on Webfaction quite easily.

Out of your description from the functionality inside your application, it does not appear too complicated, and would not be hard to scale.

PHP development atmosphere on OS X:

OS X has PHP and Apache already installed. It simply must be enabled, this site describes the procedure to have it going:


Alternatively you are able to use a package like MAMP ( http://world wide web.mamp.info/en/index.html ), which provides you with a complete stack. (And it is what I would suggest.)

The code:

For the code, you'll most likely use ASIHttpRequest to perform a Publish request to URI in your server. The script in the URI will connect with the database, keep string, after which disconnect in the database.

Under 10 lines of code.