Our photo gallery app won’t be complete until it runs on iOS, Android, and the web - all using one codebase. All it takes is some small logic changes to support mobile platforms, installing some native tooling, then running the app on a device. Let’s go!
Let’s start with making some small code changes - then our app will “just work” when we deploy it to a device.
First, we’ll update the photo saving functionality to support mobile. In the
savePicture function, check which platform the app is running on. If it’s “hybrid” (Capacitor or Cordova, the two native runtimes), then read the photo file into base64 format using the
readFile method. Also, return the complete file path to the photo using the Filesystem API. When setting the
webviewPath, use the special
Capacitor.convertFileSrc method (details here). Otherwise, use the same logic as before when running the app on the web.
Next, add a new bit of logic in the
loadSaved function. On mobile, we can directly point to each photo file on the Filesystem and display them automatically. On the web, however, we must read each image from the Filesystem into base64 format. This is because the Filesystem API uses IndexedDB under the hood. Update the
loadSaved function inside of
Our Photo Gallery now consists of one codebase that runs on the web, Android, and iOS. Next up, the part you’ve been waiting for - deploying the app to a device.