Jimmy Our app has a very similar need, Neatstreets is a reporting tool which can include many photo's taken for any given report. We store all essential report data to an internal db, which includes file names references to the images on the external Sd card (under the package named folder - as you mention).
This way the app can still function if the SDcard is swapped out, you'll just need to handle cases where images cannot be found. Useful if an important req is to maintain the ability to always raise new jobs (and your current sd becomes full). However our importance on maintaining ease of access to all previous images is probably less than yours as we also send all reports and images to the server. Rich On May 6, 7:54 pm, JimmyHoffa <[email protected]> wrote: > Thanks for reply. > > I should have stated that app will be offline and not relying on > online storage so cloud is not really appropriate as the same screen > will allow the user to grab a picture via the camera and then store > the image. I think I'll have a play with both media storage and > database, and see what works best.. > > On May 5, 8:00 pm, Kumar Bibek <[email protected]> wrote: > > > > > It really depends on the amount of space your images would take up. If > > it runs into less than 100KB, you can put them in the drawable folder. > > but, anything beyond than that is not a good practice. Your final > > apk's size will be huge. > > > the best way is to keep your images somewhere in the cloud, and access > > them through the app. > > > Thanks and Regards, > > Kumar Bibek > > > On May 5, 8:45 pm, JimmyHoffa <[email protected]> wrote: > > > > 0 vote down star > > > > Hi all, > > > > I'm just looking for some insight into what would be the best way for > > > me to store images as part of my app. > > > > I have an activity that represents a 'Job' which has a couple of > > > edittext's and underneath was planning on using the Gallery component > > > to show images relevant to this job. > > > > The job data is stored in a database (on the sdcard) so was also > > > thinking of creating a table to store 'JobImages' and having each > > > image stored as a byte array. > > > > But I'm not sure if it would be better to store the images directly on > > > sdcard under a folder structure specific to my application and the > > > job. E.g. using the job ID number as a folder name. > > > > Depending on which method I use will greatly determine the code that > > > goes into an 'adapter' that allows me to bind to the gallery component > > > so before I begin I was wondering if anyone has had the same design > > > problem and what option they chose. > > > > Thanks, > > > > -- > > > 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 > > > athttp://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 > > athttp://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 > athttp://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
