Web based or app based?

[alex5776]

I was wondering what would be better for a sounds app? (I have a lot of sounds) Should I use iWebkit5 and UIWebView to make it web based or load all of the sounds onto the app and make it using a tableview/lots of buttons and linking each one to the file. Here are my pros and cons of each.
Please reply with your own pros and cons, Thanks in advance.

Web Based

Pros

1. Light App
2. easy to update
3. less coding
4. Easy to fix if there is an error
5. I know HTML and java, etc

Cons

1. Have to find a way for the sound to play with out the movie type thing(slides up and has the play, etc)
2. make it easy to use and not slide around like in safari
3. Same styles as app
4. User must be connected to the internet for this to work
5. Idk if this is true but a friend said that if the website interacts with the app/device then it will be rejected

On App

Pros

1. Works Ofline
2. faster(mabey) because it does not need to connect to a server
3. Works along side app so I dont need fuss with styling
4. I can code all at once (good or bad)

Cons

1. app will be very, very large
2. Can easyly update sounds
3. whole new update to fix a sound or add a sound
4. Prevents use of a part of a feature(record your own sound then send it to me for approvle, then I can send it to the app right a way

Any help or thought will be amazing

[dany_dev]

a native app 99% can't compare with a web app (just google can do it ), however if your app is so simple that can be used as webapp......go with that.

[alex5776]

Originally Posted by dany_dev

a native app 99% can't compare with a web app (just google can do it ), however if your app is so simple that can be used as webapp......go with that.

I should have been more clear
Either way I will have a real app on the app store
It is how I host and post and all that good stuff that I want to know.
Online or on app?

Thank you for your help!

[AppMason Studios]

Originally Posted by alex5776

I was wondering what would be better for a sounds app? (I have a lot of sounds) Should I use iWebkit5 and UIWebView to make it web based or load all of the sounds onto the app and make it using a tableview/lots of buttons and linking each one to the file. Here are my pros and cons of each.
Please reply with your own pros and cons, Thanks in advance.

Web Based

Pros

1. Light App
2. easy to update
3. less coding
4. Easy to fix if there is an error
5. I know HTML and java, etc

Cons

1. Have to find a way for the sound to play with out the movie type thing(slides up and has the play, etc)
2. make it easy to use and not slide around like in safari
3. Same styles as app
4. User must be connected to the internet for this to work
5. Idk if this is true but a friend said that if the website interacts with the app/device then it will be rejected

On App

Pros

1. Works Ofline
2. faster(mabey) because it does not need to connect to a server
3. Works along side app so I dont need fuss with styling
4. I can code all at once (good or bad)

Cons

1. app will be very, very large
2. Can easyly update sounds
3. whole new update to fix a sound or add a sound
4. Prevents use of a part of a feature(record your own sound then send it to me for approvle, then I can send it to the app right a way

Any help or thought will be amazing

DEFINITELY Native App....

[alex5776]

Originally Posted by AppMason Studios

DEFINITELY Native App....

You saw my post before your right?


No matter what it is a native app.
It is just were I host the sound files.


Thank you for all of your help

[lgehrig1]

You do realize that 75% of the "CONS" on your app are demonstrably false, don't you?

1. You can load sounds on-demand from your server (web is easiest, but you can make any protocol you want). If the user wants cow sounds, no need to send horse.

3. If you put your catalog of sounds on your server, your app can check the version of that catalog and update itself. You do not need to send an entire app update because you've added one new MP3 file.

4. An iPhone is ... well ... a phone. It can record sounds.

Now ... your CON #2 is correct - it ** IS ** easy to update sounds, catalogs, and allow information to flow back-and-forth between the phone and your servers (Facebook, Flickr, Twitter - these are just a few of the GIANTS doing this, and ** LOTS ** of small guys do the exact same thing). Dunno why this represents a problem, but haters gotta hate!

If you are going to allow the user to apply effects & filters (reverb, distortion, high pass, low pass) then running it on the phone means your servers aren't taxed with all this nonsense, and there are several DSP's already built-in you can access to keep it as hardware-as-possible.

Turn on iTunes file sharing (UIFileSharingEnabled), and the users can drop files directly into your app's Documents directory. Make collections and let the users mix-and-match.

[harmar]

Easy, make it store the sounds on the iPhone, and then have the app poll the server once in a blue moon to get any new/updated files.

[alex5776]

Thank you guys so much.

I typed all of my cons and pros and all that stuff on my iphone and I will never make the worlds best iphone typer, and add in that stupid autocorrect.

What I think I am going to do is host the sounds on the device, and every now and then have the app update the sound list. Thank you so much for all of your help.