While not every app is built the same, what we go over in this guide is a sample of what we’ve tested and support including their subclasses. While this is not an exhaustive list, it’s meant to be a guideline on what to look out for and what’s generally an editable element in your Android app.
With Taplytics Visual Editor for Android, we cover nearly every case within a Native Android app. Anything stemming from a View can be modified in some way as well image/text related views.
Views can also be modified in nearly every layout and anything contained within them which includes:
- ListViews
- RecyclerViews
- ViewPagers
- DialogFragments
- Fragments or SupportFragments
As well as various combinations of the above. With that said, these elements combined would cover 90% of Native Android elements.
The remaining 10% is what we don’t currently support, which is challenging because of the sheer number of elements out there that we can’t guarantee coverage of elements and all their permutations and combinations.
Some examples would be:
- progress bars
- clocks
- media controllers
- WebViews
- calendars
- phone diallers
There is an infinite list of things that we can change visibility/shape of but not actually edit or change their proprietary parts.
Below is a sample of view elements that we can support and their sub-classes:
View elements
|
width/height/background/visibility/alpha/padding
|
TextView
|
text, text size, text colour, hint, gravity
|
ImageView
|
swapping images, scale type, alpha, width, height, swapping out images and more.
|
Button
|
text, hint text, text size, color, alignment, width/height, padding, hidden, background color
|
For everything else you’re curious about, we encourage our users to use this as an opportunity to test and play with your app while your experiment is in draft mode and start testing the limits of the elements you’re interested in.
Use Cases for Visual Editor on Android:
- hotfixes for errors in copy
- swapping out images to see if they can help with certain desired behaviours (more attention to Calls-To-Action buttons) or to convey more meaning to images on a screen
- creating variations of the copy on pricing page experiments
- creating variations of the copy on onboarding page experiments
- swapping out icons to see what iconography generates more engagement
- hiding elements to see if less chance there’s a measurable impact on conversions (pricing options, hiding Twitter, Google, Email, or Facebook options)
Comments
0 comments
Please sign in to leave a comment.