{"id":21836,"date":"2019-01-14T16:27:38","date_gmt":"2019-01-14T16:27:38","guid":{"rendered":"http:\/\/introducing_the_cloudinary_demo_android_app_part_2"},"modified":"2024-06-04T15:51:55","modified_gmt":"2024-06-04T22:51:55","slug":"introducing_the_cloudinary_demo_android_app_part_2","status":"publish","type":"post","link":"https:\/\/cloudinary.com\/blog\/introducing_the_cloudinary_demo_android_app_part_2","title":{"rendered":"Introducing the Cloudinary Demo Android App, Part 2"},"content":{"rendered":"

Recently we added the Cloudinary Demo- e-commerce App to the Google Play Store. This app demonstrates the best practices for optimal delivery of images on a storefront, including category pages, product pages, and a shopping cart. At the time, we published Introducing the Cloudinary Demo Android App, Part 1<\/a>, which provided an under-the-hood tour of how the eCommerce Android App was designed and how Cloudinary was integrated throughout.<\/p>\n

The app demonstrates how to leverage some of Cloudinary\u2019s capabilities, such as managing file uploads<\/a>, displaying images responsively, and optimizing delivery through global Content Delivery Networks (CDNs). The app was developed as an open source project so that you can explore the code for yourself and see how to improve your users\u2019 experience and the performance of your apps by delivering images, enhanced and optimized for different contexts.<\/p>\n

\"CloudinaryDemoApp1\" \"CloudinaryDemoApp1\" \"CloudinaryDemoApp1\"<\/p>\n

<\/div>\n

In part 2 of this series, we will focus on how the open source code that we\u2019ve published on GitHub<\/a> can also be used as the code base for developing your very own Android app, using Cloudinary for media upload, optimization, and responsive delivery.<\/p>\n

Tip:<\/strong>

Some sections in this post assume you have a basic understanding of how the Cloudinary Demo Android App is designed and structured. If you didn\u2019t get a chance to read Part 1<\/a> of this post, or it\u2019s been a while since you did, we recommend reading it before continuing.<\/p><\/div>\n

Overview<\/h2>\n

After you fork the Android Demo Application github repository, you just need to make a few basic changes to make the app your own:<\/p>\n

    \n
  1. \nConfigure your App<\/a> with the Cloud Name to your account.<\/li>\n
  2. \nUpdate the Data Flow<\/a> from the data<\/code> and remote<\/code> packages, through the repo<\/code> to the ViewModels<\/code>, and then on to the UI.<\/li>\n
  3. \nGive your Product Images Context<\/a> so that your app will use your own product images from your own Cloudinary account.<\/li>\n
  4. \nSwitch Over to a Real Backend Flow<\/a> instead of the local file implementation.<\/li>\n<\/ol>\n

    So that\u2019s it in a nutshell. The following sections go into more detail:<\/p>\n

    Configure your App<\/h2>\n

    Your App needs to be updated to use the Cloud Name of your own Cloudinary account to retrieve product images. If you don\u2019t have a Cloudinary account yet, you can easily sign up for a free account<\/a>.\nThe first step is to update the cloudName<\/code> in two places:<\/p>\n