Once your feedback form is set up and you are familiar with the tool, it's time for your developers to implement Usabilla for Apps into your app. Since the Usabilla for Apps implementation process is quite a technical one, we offer developers' documentation of the process on our Github pages for Android and iOS. This article, on the contrary, helps you to understand the implementation process from a non-technical perspective.
What are SDKs and where do I find them?
In order to implement a feedback form into your app, we provide two Software Development Kits(SDK) with which your developers can implement Usabilla for Apps. An SDK is a term, commonly used in software development, describing a package of software development tools that enable you to easily implement an existing piece of software. In our case, this is the Usabilla feedback form.
The Usabilla for Apps SDKs can be found in our Github repositories. Simply forward these links to your developers:
Through these links, your developers will be able to download the latest versions of the SDKs and access the implementation instructions.
How do I define when and where the form will be shown?
The Usabilla for Apps SDKs allows you to implement a feedback form anywhere in your app. Your developers decide when and where the form will show up. The feedback form is commonly triggered through a menu item or an icon in the corner of your app, but it can also be tied to specific features on which you would like to receive feedback.
Since your developers are free to determine when and where the feedback form will show, it can also be connected to events in your app. This way you can actively show the form to your users depending on their behavior in the app.
The Usabilla for Apps feedback form can also be triggered from multiple places in your app and you can use as many forms as you like. In order to determine which form needs to be shown, your developers will need the feedback form's id.
Which settings does my developer need to configure in the app?
Once the feedback form is implemented, there are a few settings that need to be defined in the application. For passive feedback forms these are:
- masking sensitive information in screenshots
- the style of the mood rating
- the font to be used
- custom variables
- localization of button text
- the offline feedback form in iOS
For active campaigns surveys, your developers will also need to know about:
- events for targeting
- critical moments from which campaigns should be excluded
Along with the feedback a screenshot of the screen the user is seeing can be included. This screenshot can be generated by Usabilla, provided by your application itself or uploaded by the user. If you are either generating the screenshot through Usabilla or in your application itself, the user will be able to see the screenshot while leaving feedback, with the option to delete it. If you are allowing the user to upload their own screenshot, they will be asked to upload one of the photos from their phone's library. This is not mandatory for the user.
In order to prevent users from (accidentally) submitting sensitive information through the feedback form's screenshot, you can apply masking to a self-created screenshot, before submitting it in Usabilla. The masking is not possible if you are using the screenshot that was generated by Usabilla.
Style of the mood rating
By default, the first question in the feedback form uses Usabilla's yellow default smileys. If desired, your developer can substitute the default smileys with stars or smiley images in your app's branding.
If your app is using a custom font, you can also include this font in your feedback form. Your developer will be able to specify the font in the implementation process.
Custom variables allow you to complement your feedback items with information that you have available about your user. You can, for instance, include a username, information about past purchases or an analytics ID in the feedback. Your developer can define which variables should be sent to Usabilla.
In order to replace some of our default texts in your feedback form, you can use our localization files. Localization files allow you to provide custom lines of text for standard elements in your feedback form, such as "submit", "Add a screenshot", "required question" and "Continue". The following text can be changed in your feedback form:
- Give more feedback
- Rate in the app store
- Close the form
The offline feedback form in iOS
Usabilla for Apps allows you to collect feedback regardless of whether the user is connected to the internet or not. In order to show the correct feedback form to offline users, your developer will have to preload your feedback forms through the iOS SDK. Preloading the feedback forms will load and cache the latest version of your forms. When users then open the feedback form, while they are offline, this latest version of the form will be shown. Information on how your developer can preload your forms can be found in our developers' documentation.
When users then leave feedback in your app, this feedback will be stored and sent to Usabilla as soon as the user opens the app and internet is available again. At the moment, preloading the form is only possible in iOS.
Events for campaign targeting
Campaign surveys in Usabilla for Apps are event-based. This means that your developers will need to make events in your app available for targeting. Your developers will rely on you to tell them during which moments you would like to show a survey to your users. Potentially, your developers can also implement an event handler, which provides more freedom in targeting events. Detailed information about events is available here.
Critical moments from which campaigns should be excluded
Sometimes, there are moments in your app during which you would not like to show a survey to your user. These moments are for instance when you know your users need to find information quickly or when they are doing something important such as making a purchase. Your developer can ensure that Usabilla knows when not to show a campaign.