iOS App Development - Native vs Web?

[Ancalagon]

Thanks for the replies everyone, have a clear picture now. I was told too that the Web App option will allow the app to be submitted to the Apple Store online...even though its not native app. Seems this info Im being fed is half baked. Been reading up a bit and I see the only way to get an App in the App Store for iPhone / iPad is the native route. Sure the workaround bookmark option is a good idea...but will relay the info and make an informed decision.

Company is really pushing for this, have a feeling a Mac will be purchased and the native route explored...

Appreciate the help!!

Well, no, a web app (ie a phonegap app) can still be submitted to the app store.

Its just that, whether its web or native, you need a Mac.

 

[MongooseMan]

VirtualBox the damn Mac OS if you really DO need a "Mac". Much cheaper than to faff around with a new machine

Have you actually done this?
Or are you speculating?

 

[MisterBigglesworth]

Well, no, a web app (ie a phonegap app) can still be submitted to the app store.

Its just that, whether its web or native, you need a Mac.

Even clearer now, Got it, thanks

 

[JStrike]

VirtualBox the damn Mac OS if you really DO need a "Mac". Much cheaper than to faff around with a new machine

It's also illegal. Which doesn't sit well with any decent business

 

[MongooseMan]

It's also illegal. Which doesn't sit well with any decent business

Yeah, there's that too

 

[hof]

Strictly speaking, you don't actually need a Mac for development or deployment - just for creating and configuring a provisioning profile. As soon as that's done you can use PhoneGap Build or Trigger.io to compile for iOS.

 

[MeercatMilker]

Sorry, its true.

http://docs.phonegap.com/en/2.0.0/guide_getting-started_ios_index.md.html#Getting Started with iOS

You cannot publish an app to an iOS device without a Mac. If its not an app, then its fine (ie a webpage that uses iOS's Safari)

True

 

[Gnome]

Am I the only person who is wondering why a company would ask someone so wholly uninformed if they should do a native VS HTML5 app (No offense CrazyFig, but are you even a software developer?)

Furthermore, if it is going to be used for customers/business, why on earth isn't proof of concept done.

Developing an app like that in house is incredibly expensive. A company that makes those decision with so little research is just...

Wow, that is all I can say.

 

[Wovenhand]

A company that makes those decision with so little research is just...

You'd be surprised - this is how business is done these days in "start-up world".

You probably work for a corporate?

 

[DrJohnZoidberg]

Apparently the iOS Facebook app uses HTML5 and it's the worst app I have used on my iPad. I don't know if its up to bad coding or limitations of HTML5 but maybe look at this as an example where a native app would have been much better.

 

[Gnome]

You probably work for a corporate?

I did and there we sometimes did things that way (winging it), because a few million here and there was nothing.

Now I work for a much smaller company with tight deadlines, tighter budgets and serious high output per developer. Those things go hand in hand with excellent planning and management.

 

[Wovenhand]

Of course writing natively for every platform is ideal, but that's impossible (monetarily).

HTML5 "apps" "compiled" cross-platform are going to be gash.

My personal target market would be iOS, but needing a Mac precludes me from developing for it.

 

[Nefertiti]

Am I the only person who is wondering why a company would ask someone so wholly uninformed if they should do a native VS HTML5 app (No offense CrazyFig, but are you even a software developer?)

Furthermore, if it is going to be used for customers/business, why on earth isn't proof of concept done.

Developing an app like that in house is incredibly expensive. A company that makes those decision with so little research is just...

Wow, that is all I can say.

We all had to start somewhere and had to do development tasks outside our comfort zone (with success and improvement each step). That is how people learn, right? And sometimes companies have to try out things before they know what they want, that is part of their growth and innovation process. And yes, we can argue about the pros and cons for each. Your statement makes it sound like all events start out perfect? Or am I missing the point?

 

[MisterBigglesworth]

Am I the only person who is wondering why a company would ask someone so wholly uninformed if they should do a native VS HTML5 app (No offense CrazyFig, but are you even a software developer?)

Furthermore, if it is going to be used for customers/business, why on earth isn't proof of concept done.

Developing an app like that in house is incredibly expensive. A company that makes those decision with so little research is just...

Wow, that is all I can say.

They spoke to a 3rd party dev house, and the details of the chat was relayed to me. Prob a broken telephone of sorts because the person relaying the info is not technical minded. So I think they got their signals crossed, so now Im researching the native vs web option and getting as much info as possible.

Yes, I am a developer but not an app developer. So this is new ground for me. Im a capable developer, learn quick...having being dev'ing for over 10 years...so to pick up something new, well....I have no issues with it. I learn quick and sure it will be tough and slow to start, but I know I will get there. Thing is app dev is something Im interested in, the company want an app...so we have 2 choices. One is I do it inhouse, so it might take a bit longer but the company will save on dev costs relatively speaking....or two, get a 3rd party dev company to do it...but there is a delay cos of the projects they are busy with...so they will fit us in later on. Added risk is we might not get what we actually want...this has happened a few times dealing externally. And lastly its very expensive, so as something the company wants to "explore", cost needs to be at a minimum where possible.

And how did you read we doing no research? We have met with other soft dev companies, Im doing research...actually we all are. We have not decided on anything yet, just building a path we think we will go down. Nothing has been committed to yet...nothing has been started either...

Anyways, so ja...there ya go, you up to speed now with some background info

We all had to start somewhere and had to do development tasks outside our comfort zone (with success and improvement each step). That is how people learn, right? And sometimes companies have to try out things before they know what they want, that is part of their growth and innovation process. And yes, we can argue about the pros and cons for each. Your statement makes it sound like all events start out perfect? Or am I missing the point?

Yeah, also kinda got that feeling, lol. Your reply above is spot on...its a win / win situation as I see it. I will get the exposure I want, and the company gets what they want with a cost saving Sure, I dont expect smooth sailing...but hey, we all are aware of that as its new ground for everyone

 

[Gnome]

We all had to start somewhere and had to do development tasks outside our comfort zone (with success and improvement each step). That is how people learn, right? And sometimes companies have to try out things before they know what they want, that is part of their growth and innovation process. And yes, we can argue about the pros and cons for each. Your statement makes it sound like all events start out perfect? Or am I missing the point?

I think I misunderstood the first post as saying: We are going to develop a mobile app. I've been asked what we will do, based on that we will go ahead with it.

I just think a large commitment like that should be researched by multiple people and get external input because it is very costly.

After that I would even do a small proof of concept, just a single view, to see what the pro/con is of each approach. POC doesn't take more than a week which is peanuts compared to the cost of the actual development of such an application.

They spoke to a 3rd party dev house, and the details of the chat was relayed to me. Prob a broken telephone of sorts because the person relaying the info is not technical minded. So I think they got their signals crossed, so now Im researching the native vs web option and getting as much info as possible.

Yes, I am a developer but not an app developer. So this is new ground for me. Im a capable developer, learn quick...having being dev'ing for over 10 years...so to pick up something new, well....I have no issues with it. I learn quick and sure it will be tough and slow to start, but I know I will get there. Thing is app dev is something Im interested in, the company want an app...so we have 2 choices. One is I do it inhouse, so it might take a bit longer but the company will save on dev costs relatively speaking....or two, get a 3rd party dev company to do it...but there is a delay cos of the projects they are busy with...so they will fit us in later on. Added risk is we might not get what we actually want...this has happened a few times dealing externally. And lastly its very expensive, so as something the company wants to "explore", cost needs to be at a minimum where possible.

And how did you read we doing no research? We have met with other soft dev companies, Im doing research...actually we all are. We have not decided on anything yet, just building a path we think we will go down. Nothing has been committed to yet...nothing has been started either...

Anyways, so ja...there ya go, you up to speed now with some background info

Read my response above, I think I got the wrong impression

Good luck to you guys.

But as someone who is part of a mobile dev team, we went native because it is just the best experience. I can't tell you any details but our mobile apps didn't have to change much between Android and Apple because of certain things we did.

User experience is just so much better than the mobi site.

 

[MisterBigglesworth]

I think I misunderstood the first post as saying: We are going to develop a mobile app. I've been asked what we will do, based on that we will go ahead with it.

I just think a large commitment like that should be researched by multiple people and get external input because it is very costly.

After that I would even do a small proof of concept, just a single view, to see what the pro/con is of each approach. POC doesn't take more than a week which is peanuts compared to the cost of the actual development of such an application.



Read my response above, I think I got the wrong impression

Good luck to you guys.

But as someone who is part of a mobile dev team, we went native because it is just the best experience. I can't tell you any details but our mobile apps didn't have to change much between Android and Apple because of certain things we did.

User experience is just so much better than the mobi site.

Ah cool, no worries

Yeah being a web developer Im leaning towards a web app myself so it prob came across wrong. Would love the native route, but thats just a much bigger learning curve. Will see what my company's needs are next week and then take it from there

I have been looking at PhoneGap, seems it will work for our needs....but you still need a Mac in the end. My Google searching did find one blog post detailing how this guy managed to avoid Mac's completely! Interesting read...who knows, added the link below for those interested as it seems it can all be done on Windows and no Mac is needed with PhoneGap Build

http://www.codeoutlaw.com/2011/10/ios-development-on-windows-w-phonegap.html

 

[Nefertiti]

I think I misunderstood the first post as saying: We are going to develop a mobile app. I've been asked what we will do, based on that we will go ahead with it.

I just think a large commitment like that should be researched by multiple people and get external input because it is very costly.

After that I would even do a small proof of concept, just a single view, to see what the pro/con is of each approach. POC doesn't take more than a week which is peanuts compared to the cost of the actual development of such an application.

no problem, I thought maybe its me crossing a wire or two... I agree with the research and the proof of concept, it always comes in handy. Not that always helps when you delve deeper, but comes in handy in eliminating stuff.

 

[Nefertiti]

Ah cool, no worries

Yeah being a web developer Im leaning towards a web app myself so it prob came across wrong. Would love the native route, but thats just a much bigger learning curve. Will see what my company's needs are next week and then take it from there

I have been looking at PhoneGap, seems it will work for our needs....but you still need a Mac in the end. My Google searching did find one blog post detailing how this guy managed to avoid Mac's completely! Interesting read...who knows, added the link below for those interested as it seems it can all be done on Windows and no Mac is needed with PhoneGap Build

http://www.codeoutlaw.com/2011/10/ios-development-on-windows-w-phonegap.html

hmm... I'll bookmark it for later but I'll probably just get a mac (less hassle). Waiting for the new iMacs to come out so I can get one since I want to dabble in developing an app as well.

 

[Ancalagon]

When I reach the point that I'm ready to do iOS development, I'm gonna buy a MacBook Air. Fills a niche that I need - a laptop - and solves the problem of deployment to iOS. Not cheap though.

Native development is not for the fainthearted - unless you really need it, I'd avoid it. Not that I know much about native iOS development, but from my experience with native Windows and Linux development, its much more difficult.

 

[kurtkz]

@op: Have you considered Adobe Air? You can use Javascript and repackage it using Air. You can also put the resulting installer on the various app stores...