Ensure perfect app functionality across real devices & browsers
Optimize app front end performance in real world conditions with AI insights
Catch & fix issues before users with 24/7 AI monitoring
Run manual & automated tests at scale over real devices on cloud
Validate apps across every browser-OS combination
Create and maintain end to end tests without coding
AI Agents throughout the entire testing lifecycle
Gen AI Powered Agent for End to End Testing
Transform your Own Devices into a Test Lab for On Premise Testing
As Android continues to evolve, new versions bring significant changes that affect how apps function. Android 14 introduces several behavior updates that developers must address to ensure app compatibility and maintain seamless user experiences. From security enhancements to accessibility improvements, these updates refine the platform’s efficiency and privacy while promoting better performance. Let’s explore the most important changes and how they impact app development.
Starting with Android 14, users can dismiss certain foreground notifications that were previously non-dismissible. This affects notifications that use Notification.FLAG_ONGOING_EVENT, except for specific cases like media playback, active calls, or device policy controller notifications. Developers should test their apps to ensure important notifications remain accessible while allowing unnecessary ones to be dismissed. This change grants users more control over their notifications, preventing clutter and improving usability.
Font Scaling Up to 200%
Android 14 aligns with Web Content Accessibility Guidelines (WCAG) by allowing users to scale fonts up to 200%. This is particularly useful for individuals with visual impairments, as it provides greater readability and customization of text size. Developers should verify their app’s UI responsiveness to large text sizes, ensuring that text elements do not overlap or get cut off, and that overall usability is maintained across different screen sizes and orientations.
Minimum Target API Level Requirement
To improve security and reduce vulnerabilities, Android 14 enforces a minimum targetSdkVersion of 23 for all new app installations. This means older, outdated apps that do not meet modern security standards can no longer be installed on new devices. Developers must ensure their apps comply with newer security frameworks and best practices, such as using secure storage, enforcing modern encryption techniques, and handling user data responsibly.
In Android 14, the OWNER_PACKAGE_NAME field in the media store is now redacted unless the querying app has explicit permissions (QUERY_ALL_PACKAGES) or the storing app’s package name is always visible. This update enhances user privacy by limiting access to metadata about media files. Apps that rely on accessing media ownership information will need to request appropriate permissions or adapt their workflows to accommodate this restriction.
Foreground Service Type Requirement
Apps targeting Android 14 must specify at least one foreground service type when starting a foreground service. This prevents apps from misusing foreground services, ensuring they are only used for necessary and well-defined purposes like media playback, location tracking, or health monitoring. Developers should update their app manifest and logic accordingly to comply with this requirement and avoid unexpected app terminations.
Android 14 now strictly enforces the BLUETOOTH_CONNECT permission when calling BluetoothAdapter.getProfileConnectionState(). This change prevents unauthorized access to Bluetooth connection states, enhancing user security and privacy. Developers should ensure that their apps request and handle Bluetooth permissions correctly, prompting users for approval when necessary and explaining why the permission is required.
1. Carrier Privilege Rules Parsing
Android 14 enhances OMAPI’s ability to parse and enforce carrier privileges. This ensures that only authorized apps can access certain network-based services, benefiting apps that deal with mobile payments, SIM-based authentication, and telecom services. Developers working on applications that interact with carrier networks should update their logic to incorporate these privileges seamlessly.
2. Embedded Secure Element (eSE) Access Customization
Developers now have more control over how apps interact with embedded secure elements (eSEs), including system-privileged permissions and configurable Application Identifier (AID) rules. These improvements provide more flexibility for secure transactions, identity verification, and device authentication. By leveraging these changes, app developers can create robust security measures for mobile wallets, enterprise authentication, and other security-sensitive applications.
3. Device Capability Filtering Indicators
Android 14 introduces better filtering mechanisms for detecting device capabilities related to secure elements. This helps apps determine whether a device supports necessary hardware, reducing crashes or compatibility issues. Apps that rely on specific hardware security features can now more accurately tailor their functionality based on device compatibility, offering a more streamlined user experience.
Android 14 brings numerous behavior changes designed to enhance security, accessibility, and app compatibility. Developers should proactively update their apps to align with these modifications, ensuring a seamless experience for users while leveraging the platform’s latest advancements. Staying informed about Android updates and testing apps thoroughly will be key to maintaining high performance and compliance with evolving platform standards. By adapting to these changes early, developers can ensure their apps remain secure, efficient, and user-friendly in the ever-evolving Android ecosystem.
Comments closed
We are glad to announce the release of pCloudy 5.4 with exciting new features to make app testing simpler than ever. There is a possibility that you might be familiar with pCloudy, but for those who are new, pCloudy is a cloud-based mobile app testing platform. We have achieved many milestones in a short period of time because we resolve issues immediately and bring in new features on a regular basis. Case in point: This new version of pCloudy, where we have addressed the concerns of our users and added new features to optimize testing. Let’s have a look at all the features added in pCloudy 5.4.
To test your app on a pCloudy device you need to login to device.pcloudy.com and then book a device by clicking on the devices tab. Just click on the available button next to the chosen device which will take you to the device interaction page. Earlier in the device window, you would have to use the virtual extended keyboard to enter text in the device. Although now you can just copy any text from your system and paste it in the device directly. So now instead of using an extended keyboard just use two buttons to enter the string in the device. This will save time and effort when working with multiple devices where you need to enter long text many times.
To use the FollowMe feature you will have to instrument the app you want to perform the test on. Under devices section, click on the FollowMe tab then in the next screen choose the app, select the duration and devices on which you will perform the test. In the next screen, you will see the devices which you selected and two options (Softkeys and Screenshots) at the top right corner of the window. Now when you perform any action in the master device, that action gets replicated on the secondary device too. If you enter text, tap on a button, swipe, etc. in the master device then that will happen simultaneously in the secondary device. For more information, refer to this link:-
https://www.pcloudy.com/mobile-application-testing-documentation/manual-app-testing/follow-me-app-testing.html
In pCloudy, you can run Appium tests on multiple devices in parallel. To perform a test using Appium, you need to feed in the capabilities. Some users want to test their apps more than once to perform different types of tests on the same app. To do that earlier the users had to install the app again and again. But now we have released an update through which you can perform different types of testing using Appium on the preinstalled apps. This will save you time and make the process easier. So if you have already installed the app in the device and you want to perform a test on the same app then you don’t need to pass the Application Name capability. For more information, refer to this link:-
https://www.pcloudy.com/mobile-application-testing-documentation/automation-testing/inspect-element-using-appium-desktop.html#running-appium-scripts
pCloudy is integrated with the most popular tools and frameworks to make testing convenient. A lot of users also requested to integrate Github repository and so we did it. Now you can directly upload your tasks and raise defects in the GitHub repository from pCloudy. Again this feature is added to make it convenient for our users to test and manage the tasks through pCloudy. To make use of GitHub just login to device.pcloudy.com and click on the user name at the top right corner of the window. In the dropdown list click on settings and in the settings window click on GitHub tab and enter the URL and access key to register. Now in the device session screen, you can click on Collaborate and then select Log a bug in GitHub. A new window will open where you will be able to see the list of repositories, enter the issue type, enter the title, add the description and then click on the click on the Log A Bug In GitHub button. Then you can go to the GitHub to check all the issues raised whenever you want.
We are working on some more new features and very soon we will come up with the new version of pCloudy. This is a constant process and we always try to address the users issues and provide them updates on a regular basis. This is why we are achieving new heights and we will keep on working hard to provide the best service.
Related Articles:
Your 30 minutes demo includes: