If you want to scale your application and in future also want to change these audio files then these audio files should be at some server.
it should be like: 1: Application maintains a version for audio files stored in Res. 2: Application starts, it will send version to server 3: On checking version server will tell the application if newer audio files are available or not 4: If new audio files are available then application should download new audio files from server otherwise keep on using existing audio files. Thx Dalvin On Fri, Oct 15, 2010 at 4:23 AM, dipti <[email protected]> wrote: > Hi, > > I've created an application which uses around 15 small audio files. > Right now I'm using mp3 files and each is around 200KB. These files > are stored in my res/raw directory. > I'm using SoundPool class to play the files in my application. > > I'm hoping to put this application on the android market place. > > Can one of you suggest what is the best way to store so many audio > files? Will my application be scalable? > > Is wav or ogg format better approach instead of mp3? Please let me > know. > > Thanks, > Dipti > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
