Here's 2 main factors to consider for native vs. a web-based derivative:

1. Is the app the core product? Or is it just another channel?

2. Does it absolutely need to be on more than 2 platforms?

3. Do you have enough resources? No, no one ever have enough resources. So don't worry about it.

As for Parse:

You should definitely consider Parse if it suits your requirements and helps you to ship faster. You can export the data when you are ready to move on. Ditto for most other tools like Urban Airship.

When you rely on another company's platform you are betting everything on the health and future of that platform. HTML will be around and Obj-C will be around. Will Parse? And if it isn't can you switch away quickly? I wrote about this last week, actually, if it is helpful: http://eliainsider.com/2012/08/17/live-platform-die-platform...

Not sure if you're confused about what Parse is or whether you weren't being precise with your words, but Parse _or_ native iOS app development isn't comparable.

Are you asking whether it's safe to depend on a service like Parse/Stackmob as your backend or are you asking about the pros and cons of building native apps vs html5/hybrid?

I was asking whether it's safe to depend on a service like Parse