An important part of the sales process of an app is the product demo. This may take place before or after the deal has be sealed, but either way, your client will absolutely want to preview the application that will be representing their company before it goes public.
Back office preview
The most basic way to show your client their app is by giving them access to the back office. Here, the application can be viewed on a range of mockup devices. If your client wants to be part of the design process at all, this is the quickest and easiest way to gather their input and approval before too much work goes in. If you trust their skills, you can even give them some rights to modifying certain elements.
My GoodBarber App
The next step up in previewing the app involves the actual phone or tablet. You may already be aware of the My GoodBarber app which can be an option if you aren’t using the white label option. This app can be easily downloaded from the stores, and is used to preview your app as it’s being updated in the backend. However, this is not the native version of your app, meaning that all features are not available for testing (push notifications, for example).
To showcase the native version of your app with all features, and avoid displaying GoodBarber branding, the most ideal option is to generate the AdHoc version(s) of your application, and send your client this file. This can be done by adding the unique identifier (the UDID) of your client’s phone to the list of approved devices in your developer account(s). This file will allow them to download the app directly onto their device, where they can preview it and test the exact version that will appear in the stores.
This is a great way to not only present the overall app, but to upsell features as well. You can take this opportunity to give a real time demo of extra add-ons your client may want, such as loyalty cards, beacons, and coupons. It’s much easier for a client to envision the profitability of a feature when it can be demonstrated in a real life situation, rather than just hearing a sales pitch.
Later on, when updates are made that require a rebuild and resubmission, all you have to do is send the most recent AdHoc version to your client once again, and they can test and approve this new version before it’s submitted.