×

Welcome to Knowledge Base!

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Categories
All
Mobile-Android
Connectivity for billions  |  Android Developers








Over half of all users worldwide will experience your app over a 2G
connection. To improve their experience, optimize for low-speed
connections and offline working by storing data, queuing requests, and handling
images for optimal performance.




Here you can find some tips on how to accomplish these things.



Optimize images



There are a number of ways to make images easier to download. These include serving WebP images,
dynamically sizing images, and using image-loading libraries.



Serve WebP images



  • Serve WebP files over the
    network to reduce image load times and save network bandwidth. A WebP file is often
    smaller in size than its PNG and JPG counterparts, with at
    least the same image quality. Even using lossy settings, WebP can produce a
    nearly identical image to the original. Android has included lossy WebP support since
    Android 4.0 (API level 14: Ice Cream Sandwich) and support for lossless,
    transparent WebP since Android 4.2 (API level 17: Jelly Bean).


Dynamically size images



  • Have your apps request images at the target rendering size, based on the device specification,
    and your server provide appropriately sized images. Doing this minimizes the data sent over the
    network and reduces the amount of memory needed to hold each image,
    resulting in improved performance and user satisfaction.

  • User experience degrades when users have to wait for images to
    download. Using appropriate image sizes helps to address these issues.
    Consider making image size requests based on network type or network
    quality; this size could be smaller than the target rendering size.

  • Dynamic placeholders such as
    pre-computed palette values or low-resolution thumbnails can improve
    the user experience while the image is being fetched.


Use image loading libraries



  • Your app should not fetch any image more than once. Image
    loading libraries such as Glide and Picasso
    fetch the image, cache it, and provide hooks into your Views to show
    placeholder images until the actual images are ready. Because images are
    cached, these libraries return the local copy the next time an image is
    requested.

  • Image-loading libraries manage their cache, holding onto the most recent
    images so that your app storage doesn’t grow indefinitely.



Optimize networking



You can enhance the user experience by providing an optimal
network experience.

For example, you can make your app usable offline, use

WorkManager and Room,
and deduplicate network requests.



Make your app usable offline



  • In rural location and less affluent areas, it’s
    common for devices to lose network connectivity. Creating a useful offline
    state means users can interact with your app at all times. Do this by storing data locally,
    caching data, and queuing outbound requests to action when connectivity is restored.

  • Where possible, apps shouldn’t notify users that connectivity has
    been lost. It’s only when the user performs an operation where connectivity
    is essential that the user needs to be notified.

  • When a device lacks connectivity, your app should batch up network
    requests—on behalf of the user—that can be executed when
    connectivity is restored. An example of this is an email client that allows
    users to compose, send, read, move, and delete existing mails even when the
    device is offline. These operations can be cached and executed when
    connectivity is restored. In doing so, the app is able to provide a similar
    user experience whether the device is online or offline.



Use Room to fetch and cache data



  • Ensure that your app stores all data on disk using a database or similar
    structure so that it performs optimally regardless of network conditions.
    Use the Room persistence
    library to cache data in a local database, and use
    WorkManager to update
    that cache when the device has a network connection.

  • Apps should cache content that is fetched from the network. Before making
    subsequent requests, apps should display locally cached data. This ensures
    that the app is functional regardless of whether the device is offline or
    on a slow or unreliable network.


Deduplicate network requests



  • An offline-first architecture initially tries to fetch data from local
    storage and, failing that, requests the data from the network. After being
    retrieved from the network, the data is cached locally for future
    retrieval. This helps to ensure that network requests for the same piece of
    data only occur once—with subsequent requests satisfied locally. To
    achieve this, use a local database for long-lived data (usually
    android.database.sqlite or
    SharedPreferences ).

  • This architecture also simplifies an app’s flow between offline and
    online states as one side fetches from the network to the cache, while the
    other retrieves data from the cache to present to the user.

  • For transitory data, use a bounded disk cache such as a DiskLruCache .
    Data that doesn’t typically change should only be requested once over
    the network and cached for future use. Examples of such data are images and
    non-temporal documents like news articles or social posts.



Fine-tune data transfer



There are several ways in which your app can adapt to network conditions to provide a
better user experience. For example, it can prioritize network requests to minimize
the user's waiting time for information. It can also detect and adapt to slower network
speeds and changes that may take place in the network connection.




Prioritize bandwidth



  • You shouldn't assume that any network that the device is
    connected to is long-lasting or reliable. For this reason, apps should
    prioritize network requests to display the most useful information to the
    user as soon as possible.

  • Presenting users with visible and relevant information immediately is a
    better user experience than making them wait for information that might not
    be necessary. This reduces the time that the user has to wait and
    increases the usefulness of the app on slow networks.

  • To achieve this, sequence your network requests such that text is
    fetched before rich media. Text requests tend to be smaller, compress
    better, and hence transfer faster, meaning that your app can display useful
    content quickly. For more information on managing network requests, visit
    the Android training on Managing Network
    Usage.


Use less bandwidth on slower connections



  • The ability for your app to transfer data in a timely fashion is
    dependent on the network connection. Detecting the quality of the network
    and adjusting the way your app uses it can help provide an excellent user
    experience.

  • You can use the following methods to detect the underlying network
    quality. Using the data from these methods, your app should tailor its use
    of the network to continue to provide a timely response to user actions:

    • ConnectivityManager >
      isActiveNetworkMetered()

    • ConnectivityManager >
      getActiveNetworkInfo()

    • ConnectivityManager >
      getNetworkCapabilities(Network)

    • TelephonyManager >
      getNetworkType()



  • On slower connections, consider downloading only lower-resolution media
    or perhaps none at all. This ensures that your users can use
    the app on slow connections. Where you don’t have an image or the image is
    still loading, you should always show a placeholder. You can create a
    dynamic placeholder by using the
    Palette library to generate placeholder colors that match the target
    image.

  • On devices powered by Android 7.0 (API level 24) and higher,
    users can turn on the
    Data Saver setting, which helps minimize data use. Android 7.0
    extends ConnectivityManager to detect Data Saver
    settings. For more information about this feature, see
    Data Saver.


Detect network changes, then change app behavior



  • Network quality is not static; it changes based on location, network
    traffic, and local population density. Apps should detect changes in
    network and adjust bandwidth accordingly. By doing so, your app can tailor
    the user experience to the network quality. Detect network state using
    these methods:

    • ConnectivityManager >
      getActiveNetworkInfo()

    • ConnectivityManager >
      getNetworkCapabilities(Network)

    • TelephonyManager >
      getDataState()



  • As the network quality degrades, scale down the number and size of
    requests. As the connection quality improves, you can scale up your
    requests to optimal levels.

  • On higher quality, unmetered networks, consider
    prefetching data to make it available ahead of time. From a user
    experience standpoint, this might mean that news reader apps fetch
    three articles at a time on 2G but fetch twenty articles at a time on
    Wi-Fi. For more information on adjusting app behavior based on network changes,
    visit the Android training on
    Monitoring the Connectivity Status.

  • The broadcast
    CONNECTIVITY_CHANGE is sent when a change in network
    connectivity occurs. When your app is in the foreground, you can call
    registerReceiver to receive this broadcast. After receiving
    the broadcast, you should reevaluate the current network state and adjust
    your UI and network use appropriately. You shouldn't declare this receiver
    in your manifest, as it's unavailable in Android 7.0 (API level 24)
    and higher.
    For more information about this and other changes in Android 7.0,
    see
    Android 7.0 Changes.







Additional resources


To learn more about supporting a variety of connection speeds, view the following
resource:


Blog post



  • Connect,
    No Matter the Speed











Core app quality  |  Android Developers







This is an archived copy, last updated on February 10, 2021. You can also
view the current
guidelines.


This checklist defines a set of core quality criteria and associated tests to help you assess the
quality of your app. Some of these criteria might be easy to miss, and the tests help you remember
to include them in your test plans.



The checklist highlights the minimum quality that all apps should meet. Your testing will likely
go well beyond what's described here.



Each item in the quality checklist has a unique ID which you might find
helpful to use when you communicate with your team.



Visual experience




Your app should provide standard Android visual design
and interaction patterns where appropriate, for a consistent and intuitive
user experience.



We recommend using Material Design Components
for creating a user interface in place of Android
platform components where possible. This enables the modern Android look and feel, and it helps
provide UI consistency across Android versions.
















































































Area ID Tests Description
Navigation VX-N1 CR-3 The app supports standard Back button navigation and does not make use of any custom, on-screen "Back button" prompts.
VX-N2 CR-3 The app supports gesture navigation for going back / going to the home screen.
VX-N3 CR-1
CR-3
CR-5

The app correctly preserves and restores user or app state.


The app preserves user or app state when leaving the foreground and prevents accidental data loss due to back-navigation and other state changes.


When returning to the foreground, the app should restore the preserved state and any significant stateful transaction that was pending. Examples include: changes to editable fields, game progress, menus, videos, and other sections of the app or game.



  1. When the app is resumed from the Recents app switcher, the app returns the user to the exact state in which it was last used.
  2. When the app is resumed after the device wakes from the sleep (locked) state, the app returns the user to the exact state in which it was last used.
  3. When the app is relaunched from Home or All Apps, it should do one of the following, depending on how much time has passed since it was last used:

    • If the app was last used a short time ago (minutes), restore the app state as close as possible to its previous state.
    • If more time has passed since the app was last used, try to restore the app as close as possible to its previous state;
      or start it from its home screen or some other default state.




Notifications VX-S1 CR-9

Notifications follow Material Design guidelines. In particular:




  1. Notifications are not used for cross-promotion, or advertising another product, as this is strictly prohibited by the Play Store.
  2. Appropriately define Notification Channels according to best practices, rather than serving all notifications from one channel.
  3. Selecting the correct notification priority.
  4. Multiple notifications are stacked into a single notification group, where possible.
  5. Set timeouts for notifications where appropriate.
  6. Notifications are persistent only if related to ongoing events, such as music playback (more under the Functionality section) or a phone call.


VX-S2 CR-9

For messaging / social apps and conversations:




  1. Use the MessagingStyle notifications for conversations.
  2. Support the direct reply action.
  3. Support conversation shortcuts, and implement best practices for getting the best direct share ranking.
  4. Support bubbles.


UI and Graphics VX-U1 CR-5 The app supports both landscape and portrait orientations (if possible).


Orientations expose largely the same features and actions and preserve functional parity. Minor changes in content or views are acceptable.


VX-U2 CR-5 The app uses the whole screen in both orientations and does not letterbox to account for orientation changes.


Minor letterboxing to compensate for small variations in screen geometry is acceptable.


VX-U3 CR-5 The app correctly handles rapid transitions between display orientations without rendering problems or losing state.
Visual quality VX-V1 CR-all

The app displays graphics, text, images, and other UI elements without noticeable distortion, blurring, or pixelation.



  1. The app should use vector drawables where possible.
  2. The app provides high-quality graphics for all targeted screen sizes and form factors.
  3. No aliasing at the edges of menus, buttons, and other UI elements is visible.


VX-V2 CR-all

The app displays text and text blocks in an acceptable manner for each of the app’s supported languages.



  1. Composition is acceptable in all supported form factors.
  2. No cut-off letters or words are visible.
  3. No improper word wraps within buttons or icons are visible.
  4. There is sufficient spacing between text and surrounding elements.


VX-V3 CR-all The app’s content, and all web contents referred to by the app, support dark theme.






Functionality





Your app should implement the expected functional behavior.















































































Area ID Tests Description
Audio FN-A1 CR-1
CR-8
Audio resumes when the app returns to the foreground, or indicates to the user that playback is in a paused state.
FN-A2 CR-1
CR-2
CR-8
If audio playback is a core feature, the app should support background playback.
FN-A3 CR-0

When the user initiates audio playback, the app should do one of the following within one second:



  1. Start playing the audio.
  2. Provide a visual indicator that the audio data is being prepared.


FN-A4 CR-0 The app should request audio focus when audio starts playing and abandon audio focus when playback stops.
FN-A5 CR-0 The app should handle other apps’ requests for audio focus. For example, an app might reduce playback volume when another app plays speech.
Media FN-M1 CR-0
CR-6
CR-8
If the app plays audio in the background, it must create a Notification styled with MediaStyle.
FN-M2 CR-0 If the app plays video, it should support picture-in-picture playback.
FN-M3 CR-0 If the app encodes video, it should do so using the HEVC video compression standard.
Sharing FN-S1 CR-0 The app should use the the Android Sharesheet when sharing content.
It can suggest targets that are unavailable to custom solutions.
Background Service FN-B1 CR-6 The app avoids running background services where possible. To ensure the smooth running of the user’s device, the system applies various restrictions on background services. These are not considered good uses of background services:


  • Maintaining a network connection for notifications
  • Maintaining a Bluetooth connection
  • Keeping the GPS powered-on


Learn how to choose the right solution for your work.


FN-B2 CR-10 The app properly supports the power management features that were introduced in Android 6.0 (Doze and App Standby). In the case where core functionality is disrupted by power management, only qualified apps may request an exemption. See Support for other use cases in Doze and App Standby.








Performance and stability





Your app should provide the performance, stability, compatibility, and
responsiveness expected by users.








































































Area ID Tests Description
Stability
PS-S1 CR-all
SD-1
The app does not crash or
block the UI thread causing ANR (Android Not
Responding”) errors. Utilize
Google
Play’s pre-launch report to identify potential stability issues. After deployment, pay
attention to the Android Vitals page in the Google
Play developer console.
Performance PS-P1 CR-all
SD-1
The app loads quickly or provides onscreen feedback to the user (a progress indicator or similar cue) if the app takes longer than two seconds to load.
PS-P2 CR-all
SD-1
Apps should render frames every 16ms to achieve 60 frames per second. Developers can use the Profile HWUI rendering option in testing. If there are issues, tools are available to help diagnose slow rendering.
PS-P3 PM-1 With StrictMode enabled (see StrictMode Testing, below), no red flashes (performance warnings from StrictMode) are visible when testing the app. Any red flashes indicate bad behaviors regarding storage, network access, or memory leaks.
SDK PS-T1 CR-0 The app runs on the latest public version of the Android platform without crashing or severely impacting core functionality.
PS-T2 SP-1 The app targets the latest Android SDK by setting the targetSdk value.
PS-T3 SP-1 The app is built with the latest SDK by setting the compileSdk value.
PS-T4 SP-2
SP-3
Any third-party SDKs used are up-to-date. Any improvements to these SDKs, such as stability, compatibility, or security, should be available to users in a timely manner.

The developer is accountable for the entire app’s codebase, inclusive of any third-party SDKs used.
PS-T5 CR-0 The app does not use non-SDK interfaces.
Battery PS-B1 BA-1 The app properly supports the power management features that were introduced in Android 6.0 (Doze and App Standby). In the case where core functionality is disrupted by power management, only qualified apps may request an exemption. During development, developers can test app standby and doze behavior using these ADB commands.


In terms of battery usage, developers can use the Android Studio energy profiler or the Battery Historian tool, combined with planned background work, to diagnose unexpected battery use.








Privacy & security





Your app should handle user data and personal information safely,
with the appropriate level of permission.




In addition to this checklist, applications published on the Google Play
Store must also follow the User Data
policies to protect users' privacy.





















































































































































Area ID Tests Description
Permissions
SC-P1 SC-4 The app requests only the absolute minimum number of permissions that it needs to support its use case at hand. For some permissions such as location, use coarse location in place of fine location if possible.
SC-P2


The app should only request permission to access sensitive data (such as
SMS, Call Log, or
Location)
or services that cost money (such as Dialer or SMS) if it’s directly related to the core
use cases of the apps. Implications related to these permissions should be prominently disclosed to the user.



Depending on how you are using the permissions, there might be an
alternative way
to fulfill your app's use case without relying on access to sensitive information. For example, instead of
requesting permissions related to a user’s contacts, it may be more appropriate to request access
by using an implicit intent.


SC-P3 CR-0 The app requests runtime permissions in context, when the functionality is requested, rather than upfront during app startup.
SC-P4 CR-0

The app should design its UX to clearly convey why certain permissions are needed. If that’s
not possible, it should follow the recommended flow to
explain why a feature in your app needs a permission.


The app should gracefully degrade when
users deny or revoke a permission. The app should not prevent the user from accessing the app altogether.


Data & Files SC-DF1 SC-1 All sensitive data is stored in the app's internal storage.
SC-DF2 SC-10 No personal or sensitive user data is logged to the system log or an app-specific log.
SC-DF3 The app should not use any non-resettable hardware IDs, such as the IMEI, for identification purposes.
Identity SC-ID1 CR-0 Provide hints to autofill account credentials and other sensitive information, such as credit card info, physical address, and phone number.
SC-ID2 CR-0 Integrate One Tap for Android for a seamless sign in experience.
SC-ID3 CR-0 Integrate biometric authentication to protect financial transactions or sensitive information, such as important user documents.
App Components SC-AC1 SC-5 Only application components that share data with other apps , or components that should be invoked by other apps , are exported.


This includes activities, services, broadcast receivers, and especially content providers.



Always set the android:exported attribute explicitly to minimize confusion on the default value.


SC-AC2 CR-0
SC-4

All intents and broadcasts follow best practices:



  1. Use explicit intents if the destination application is well defined.
  2. Use Intents to defer permissions to a different app that already has the permission.
  3. Share data securely across apps.
  4. Intents that contain a payload are verified before use.
  5. If you need to pass an Intent to another app, so that the receiving app can invoke and expect a callback in the calling app, do not include a nested intent in the extras. Use a PendingIntent.
  6. When setting up your PendingIntents, explicitly set the immutable flag, where applicable.


SC-AC3 SC-3 All content providers that share content between your apps use android:protectionLevel="signature" for custom permissions. This includes activities, services, broadcast receivers, and especially content providers.

Most apps should not rely on accessing a list of installed packages. The access has been restricted beginning in Android 11.

Networking
SC-N1 SC-9 All network traffic is sent over SSL.
SC-N2 SC-6 The application declares a network security configuration.
SC-N3 If the application uses Google Play services, the security provider is initialized at application startup.
Libraries
SC-U1 SP-2 All libraries, SDKs, and dependencies are up to date.
SC-U2 No debug libraries are included in the production app. This can cause performance as well as security issues.
WebViews
SC-W1 SC-6 Do not use setAllowUniversalAccessFromFileURLs() for accessing local content. Instead, use WebViewAssetLoader.
SC-W2 SC-7 WebViews should not use addJavaScriptInterface() with untrusted content.


On Android 6.0 and above, use HTML message channels instead.


Execution SC-E1 The app does not dynamically load code from outside the app's APK. Developers should use Android App Bundles, which includes Play Feature Delivery and Play Asset Delivery.


Starting August 2021, the use of Android App Bundles will become mandatory for all new apps in the Google Play store.


Cryptography SC-C1 The app uses strong, platform-provided cryptographic algorithms and a random number generator. Also, the app does not implement custom algorithms.




Google Play





Be sure that your apps can be published on Google Play.























































Area ID Tests Description
Policies GP-P1 GP-all The app strictly adheres to the terms of the Google Play Developer Content Policy and does not offer inappropriate content, does not use the intellectual property or brand of others, and so on.
GP-P2 GP-1 The app maturity level is set appropriately, based on the Content Rating Guidelines.
App Details Page GP-D1 GP-1
GP-2

The app’s feature graphic follows the guidelines outlined in this
support article. Make sure that:



  1. The app listing includes a high-quality feature graphic.
  2. The feature graphic does not contain device images, screenshots, or small text that will be illegible when scaled down and displayed on the smallest screen size that your app is targeting.
  3. The feature graphic does not resemble an advertisement.


GP-D2 GP-1 The app’s screenshots and videos do not show or reference non-Android devices.
GP-D3 GP-1 The app’s screenshots or videos do not represent the content and experience of your app in a misleading way.
User Support GP-X1 GP-1 Common user-reported bugs in the Reviews tab of the Google Play page are addressed if they are reproducible and occur on many different devices. If a bug occurs on only a few devices, you should still address it if those devices are particularly popular or new.





Setting up a test environment





For the purpose of setting up a test environment for this checklist, we recommend the following:



  • Focused on emulator testing - Android Emulator is a great way to test your app under different Android versions and screen resolutions. You should set up emulated devices (AVDs) to represent the most common form factors and hardware/software combinations for your target user base.
  • Hardware devices - Your test environment should include a small number of actual hardware devices that represent the key form factors and hardware/software combinations that are currently available to consumers. It's not necessary to test on every device that's on the market — rather, you should focus on a small number of representative devices, even using one or two devices per form factor.
  • Device test labs - You can also use third party services, such as Firebase Test Lab, to test your app on a wider variety of devices.
  • Test with the latest Android version - In addition to testing representative Android versions for your target user base, you should always test against the latest version of Android (currently Android 11). This ensures that the latest behavior changes do not negatively impact your user’s experience.



For more comprehensive guidance on testing including unit testing, integration testing and UI testing, check out the Android testing fundamentals.





Test procedures





These test procedures help you discover various types of quality issues in
your app. You can combine the tests or integrate groups of tests together in
your own test plans. See the sections above for references that associate
criteria with these test procedures.









































































































































Type Test Description
Core Suite CR-0

Navigate to all parts of the app — all screens, dialogs, settings, and all user flows.



  1. If the application allows for editing or content creation, game play, or media playback, make sure to test those flows.

  2. While testing the app, introduce interruptions from other apps, such as receiving a notification or a phone call; and apply transient changes to device attributes, such as network connectivity, battery function, GPS availability, and system load.

  3. Enter and test all in-app purchase flows


CR-1 From each app screen, press the device's Home key or swipe up in gesture navigation, then re-launch the app from the All Apps screen.
CR-2 From each app screen, switch to another running app, and then return to the app under test using the Recents app switcher.
CR-3 From each app screen (and dialogs), press the Back button or use the back swipe gesture.
CR-5 From each app screen, rotate the device between landscape and portrait orientation at least three times.
CR-6 Switch to another app to send the test app into the background. Go to Settings and check whether the test app has any services running while in the background. In Android 4.0 and higher, go to the Apps screen and find the app in the "Running" tab.
CR-7 Press the power button to put the device to sleep, then press the power button again to wake the screen.
CR-8 Set up a screen lock on the device. Press the power button to put the device to sleep (which locks the device). Then, press the power button again to wake the screen and unlock the device.
CR-9 Trigger and observe in the notifications drawer all types of notifications that the app can display. Expand notifications where applicable (Android 4.1 and higher), and tap on all available actions.
CR-10 Review Support for other use cases in Doze and App Standby.
Install on SD Card SD-1 Repeat Core Suite with the app installed to a device’s SD card (if the app supports this installation method).


To move the app to SD card, you can use Settings > App Info > Move to SD Card.


Performance and Stability SP-1 Review the Android manifest file and build configuration to ensure that the application is built against the latest available SDK ( targetSdk and compileSdk ).
SP-2 Review the build.gradle file for any outdated dependencies.
SP-3 Use the Android Studio lint tool to detect non-SDK interface usage. Other alternative testing methods also exist.
Performance Monitoring PM-1 Repeat Core Suite with StrictMode profiling enabled.


Pay close attention to garbage collection and its impact on the user experience.


Battery
BA-1 Repeat Core Suite across Doze and App Standby cycles.


Pay close attention to alarms, timers, notifications, syncs, and so on. See Testing with Doze and App Standby for requirements and guidelines.


Security SC-1 Review all data stored in external storage.
SC-2 Review how the data that’s loaded from external storage is handled and processed.
SC-3 Review all content providers defined in the Android manifest file. Make sure each provider has an appropriate protectionLevel .
SC-4 Review all permissions that your app requires, in the manifest file, at runtime, and in the app settings screen (Settings > App Info) on the device.
SC-5 Review all application components defined in the Android manifest file for the appropriate export state. The exported property must be set explicitly for all components.
SC-6 Review the app's Network Security configuration, ensuring that no lint checks on the configuration fail.
SC-7 For each WebView, navigate to a page that requires JavaScript.
SC-8 In each WebView, attempt to navigate to sites and content that aren’t loaded directly by your app.
SC-9 Declare a Network Security Configuration that disables cleartext traffic, then test the app.
SC-10 Run the application and exercise all core functionality, while observing the device log. No private user information should be logged.
Google Play GP-1 Sign into the Google Play Developer Console to review your developer profile, app description, screenshots, feature graphic, content rating and user feedback.
GP-2 Download your feature graphic and screenshots, and scale them down to match the display sizes on the devices and form factors that you are targeting.
GP-3 Review all graphical assets, media, text, code libraries, and other content that’s packaged in the app or expansion file download.




Testing with StrictMode



For performance testing, we recommend enabling StrictMode in your
app and using it to catch operations that could affect performance, network accesses, file
reads/writes, and so on. Look for potentially problematic operations both on the main thread and on
other threads.

You can set up a per-thread monitoring policy using
StrictMode.ThreadPolicy.Builder
and enable all supported monitoring in the
ThreadPolicy using
detectAll() .

Make sure to enable visual notification of policy violations for the
ThreadPolicy using
penaltyFlashScreen() .







Read article

Still Thinking?
Give us a try!

We embrace agility in everything we do.
Our onboarding process is both simple and meaningful.
We can't wait to welcome you on AiDOOS!