After you create an insert, you will want to test it before publishing to your users. When testing, here are some items to consider:
- Screen size and screen identification - When you define a screen at Insert, you mark specific app elements to help us identify the screen. We call those elements identifying elements. The selection of these elements is crucial for correct screen identification. It is important to note that some of those elements might not be visible on small screens, which can cause the screen to not be identified. We recommend testing with different screen sizes to ensure correct screen identification.
- Dates within identifying elements - try not to select labels with dates as your screen identifying elements. Each device presents dates differently depending on the specific date format settings, this may hinder the screen identification.
- Screen size and insert display - An insert might look different on different screen sizes. Depending on the specific content, a user may have to scroll to see the entire insert on some screen sizes. Though scrolling can be okay in some cases, you should test on various screen sizes to understand the user experience.
- Different Android versions - Different Android versions may include changes to native components. Most changes occur between different Android API versions (see here for the list of Android versions). Since Insert triggers rely on native components, there are rare cases where a specific component in your app behaves differently between different Android versions. This can lead to an insert not being triggered. We recommend testing with different Android versions. The Insert engineering team also tests with multiple Android versions.