eveloping on iPhone (1): webapps or native applications?
Author: jack // Category: IPhone Application Development
In ActualidadIphone going to start running a series of posts dedicated to users who intend to make application development for our favorite gadget, of course, iPhone. Although there is a wealth of information already available, we will try to publish a series of simple guides showing, step by step, what is essential to begin to develop our applications.
Before you start, we could make some considerations:
If you do not have any training or experience in application development, it probably can move evil. In any case, in this world triumph adventurers
Most cases go for the 3G iPhone, especially by the large range of possibilities that open with the GPS.
If you have experience in developing dynamic web applications, namely knowledge of HTML, CSS, javascript, and some language or framework server (PHP, Java, rubyonrails, Python ...), without a doubt have the foundation needed to begin to develop webapps .
If you have knowledge or experience in development with Objective C (Cocoa, etc.). You can quickly begin to develop native applications for iPhone. Otherwise you will cost more. If someone had said that Objective C is very similar to Java, believe me, this is not the case
OK, but what is this for webapps and native applications? We will try to clarify these concepts, and list the main advantages and disadvantages of each of these worlds.
Webapps. The webapps are normal web applications, like any of those already familiar with. They are therefore programmed server languages (PHP, Java ...) that generate HTML with CSS layout and behavior with JavaScript. Applying specific CSS style sheets, we can give our Web applications appear 100% adapted to the iPhone, getting that looks like a desktop application. Apple offers a catalog of various applications, though no doubt most of you have already used, consciously or unconsciously, several: Google web applications (Gmail, Reader, etc.).'s Own mobile version of Facebook, and so on.
Advantages:
Do not rely on Apple for us to adopt the high of our application, or to publish a new version that includes new features or correct bugs.
Users do not need to use our applications Jailbreak, will be accessible via Safari.
Developing agile and quick.
No need to learn Objective C.
If you already have a web application, we can create a Verson iPhone.
No need to register as an iPhone Developer and pay to start the process of registering an application on AppStore.
We do not need a Mac to have the IDE development (XCode). Well, for me that's more an inconvenience, but there are still many users of other operating systems
Disadvantages:
We do not have natural access to the API's iPhone as camera, GPS, accelerometer, vibration ... there are several initiatives that seek to expose this type of advanced features for API's javascript, with varying degrees of success, but today Apple This has not standardized.
We have no link to the AppStore, which undoubtedly will lose access to a perfect showcase for our developments. However, we will always be Google
Native applications. Are the applications that we already know it all and continually since we installed the AppStore (or Cydia for jailbroken iPhones). Being developed with Objective C (although beginning to appear in webapps initiatives to transform native applications).
Advantages:
They have total access to the API's referred to as GPS, accelerometer, camera ...
If we approve Apple (which is much suppose), our application can be accessed from a large number of users.
We have the option to charge for our application, a simple business model.
Disadvantages:
We must develop in Objective C.
We have to register as Apple developers, and pay for you to test our developments in our own iPhone (!) And be able to send applications for approval in the AppStore.
In the following posts will start with the development of native applications. Prepare your team!
Before you start, we could make some considerations:
If you do not have any training or experience in application development, it probably can move evil. In any case, in this world triumph adventurers
Most cases go for the 3G iPhone, especially by the large range of possibilities that open with the GPS.
If you have experience in developing dynamic web applications, namely knowledge of HTML, CSS, javascript, and some language or framework server (PHP, Java, rubyonrails, Python ...), without a doubt have the foundation needed to begin to develop webapps .
If you have knowledge or experience in development with Objective C (Cocoa, etc.). You can quickly begin to develop native applications for iPhone. Otherwise you will cost more. If someone had said that Objective C is very similar to Java, believe me, this is not the case
OK, but what is this for webapps and native applications? We will try to clarify these concepts, and list the main advantages and disadvantages of each of these worlds.
Webapps. The webapps are normal web applications, like any of those already familiar with. They are therefore programmed server languages (PHP, Java ...) that generate HTML with CSS layout and behavior with JavaScript. Applying specific CSS style sheets, we can give our Web applications appear 100% adapted to the iPhone, getting that looks like a desktop application. Apple offers a catalog of various applications, though no doubt most of you have already used, consciously or unconsciously, several: Google web applications (Gmail, Reader, etc.).'s Own mobile version of Facebook, and so on.
Advantages:
Do not rely on Apple for us to adopt the high of our application, or to publish a new version that includes new features or correct bugs.
Users do not need to use our applications Jailbreak, will be accessible via Safari.
Developing agile and quick.
No need to learn Objective C.
If you already have a web application, we can create a Verson iPhone.
No need to register as an iPhone Developer and pay to start the process of registering an application on AppStore.
We do not need a Mac to have the IDE development (XCode). Well, for me that's more an inconvenience, but there are still many users of other operating systems
Disadvantages:
We do not have natural access to the API's iPhone as camera, GPS, accelerometer, vibration ... there are several initiatives that seek to expose this type of advanced features for API's javascript, with varying degrees of success, but today Apple This has not standardized.
We have no link to the AppStore, which undoubtedly will lose access to a perfect showcase for our developments. However, we will always be Google
Native applications. Are the applications that we already know it all and continually since we installed the AppStore (or Cydia for jailbroken iPhones). Being developed with Objective C (although beginning to appear in webapps initiatives to transform native applications).
Advantages:
They have total access to the API's referred to as GPS, accelerometer, camera ...
If we approve Apple (which is much suppose), our application can be accessed from a large number of users.
We have the option to charge for our application, a simple business model.
Disadvantages:
We must develop in Objective C.
We have to register as Apple developers, and pay for you to test our developments in our own iPhone (!) And be able to send applications for approval in the AppStore.
In the following posts will start with the development of native applications. Prepare your team!
0 Responses to "eveloping on iPhone (1): webapps or native applications?"
Post a Comment