Hyperion-Shared-Preferences
Posted: Mon Dec 23, 2024 4:28 am
Thanks to this plugin you can edit your app’s shared preferences and do some crazy stuff like corrupting your refresh token and testing the app’s state in various extreme cases.
Hyperion-Attributes-Inspector. Plugin for inspecting properties of UI elements on the screen. Some properties are editable from the attribute inspector level. You can change textView and see how long strings inside your app’s layout can be.
Hyperion-Measurement-Inspector. As the name suggests, it is a plugin for pixel perfect testing of your app. You can measure the distance between UI elements and compare it to the design bulgaria mobile number from your lovely designer (very useful).
Hyperion-Crash-Plugin. Thanks to this plugin, you can see crash log right away and have some bite of information about this crash. It is nice to have some piece of it and investigate it before reporting.
Still, you can use Crashlytics, etc. but it is nice to have this plugin and see crash log right away when it occurs
Hyperion-Phoenix-Plugin – with this you don’t need to clear app data from the device settings. This plugin will help you to save time because it enables you can clean the app’s internal storage data and restart the process from your debug menu.
Third-party plugins examples
Third-party plugins add new functionalities for debug menu or add integration of existing QA tools with Hyperion.
Here are a few examples of third-party plugins:
Hyperion-Chuck by my opinion the most useful plugin for Hyperion. It integrates existing Chuck library for inspecting OkHttp traffic which I use a lot.
The simplest use-case for it: when you have some issues within the app and you don’t know exactly what happened and you want to investigate it (e.g. login fails).
With this plugin, the first thing you do is to check OkHttp traffic to tell if this bug is in the app or maybe those are server issues.
I highly recommend this plugin because it’s extremely handy and easy to use.
Hyperion-Simple-Item my second favorite plugin. It allows you to add a custom tab in the Hyperion menu.
In my implementation, I use it to create a field with device info such as device name and OS version. Having this information is very handy when reporting bugs because it’s super important to give some info about the device in your report.
Hyperion implementation
Let’s plug this nice piece of code into the app.
1. Gradle configuration
Generally, Gradle configuration is very simple. All you need to do is to follow guidelines from the Hyperion repositories. Here are a few helpful links:
Hyperion core
Hyperion chuck plugin
Chuck library itself
2. BuildVariants configuration
You would like to have Hyperion configured to target the exact buildType or flavor because you probably don’t want users to see it.
In this case, the configuration is also simple because the libraries listed above use no-op implementation. So you can have:
Hyperion-Attributes-Inspector. Plugin for inspecting properties of UI elements on the screen. Some properties are editable from the attribute inspector level. You can change textView and see how long strings inside your app’s layout can be.
Hyperion-Measurement-Inspector. As the name suggests, it is a plugin for pixel perfect testing of your app. You can measure the distance between UI elements and compare it to the design bulgaria mobile number from your lovely designer (very useful).
Hyperion-Crash-Plugin. Thanks to this plugin, you can see crash log right away and have some bite of information about this crash. It is nice to have some piece of it and investigate it before reporting.
Still, you can use Crashlytics, etc. but it is nice to have this plugin and see crash log right away when it occurs
Hyperion-Phoenix-Plugin – with this you don’t need to clear app data from the device settings. This plugin will help you to save time because it enables you can clean the app’s internal storage data and restart the process from your debug menu.
Third-party plugins examples
Third-party plugins add new functionalities for debug menu or add integration of existing QA tools with Hyperion.
Here are a few examples of third-party plugins:
Hyperion-Chuck by my opinion the most useful plugin for Hyperion. It integrates existing Chuck library for inspecting OkHttp traffic which I use a lot.
The simplest use-case for it: when you have some issues within the app and you don’t know exactly what happened and you want to investigate it (e.g. login fails).
With this plugin, the first thing you do is to check OkHttp traffic to tell if this bug is in the app or maybe those are server issues.
I highly recommend this plugin because it’s extremely handy and easy to use.
Hyperion-Simple-Item my second favorite plugin. It allows you to add a custom tab in the Hyperion menu.
In my implementation, I use it to create a field with device info such as device name and OS version. Having this information is very handy when reporting bugs because it’s super important to give some info about the device in your report.
Hyperion implementation
Let’s plug this nice piece of code into the app.
1. Gradle configuration
Generally, Gradle configuration is very simple. All you need to do is to follow guidelines from the Hyperion repositories. Here are a few helpful links:
Hyperion core
Hyperion chuck plugin
Chuck library itself
2. BuildVariants configuration
You would like to have Hyperion configured to target the exact buildType or flavor because you probably don’t want users to see it.
In this case, the configuration is also simple because the libraries listed above use no-op implementation. So you can have: