Mobile – TreeTeq https://treeteq.com Wed, 10 Jul 2024 08:10:40 +0000 en-GB hourly 1 https://wordpress.org/?v=7.0 https://treeteq.com/wp-content/uploads/2024/07/cropped-treeteq_logo-32x32.png Mobile – TreeTeq https://treeteq.com 32 32 Your app is affected by Google Play’s target API level requirements https://treeteq.com/your-app-is-affected-by-google-plays-target-api-level-requirements/ https://treeteq.com/your-app-is-affected-by-google-plays-target-api-level-requirements/#respond Wed, 10 Jul 2024 08:12:01 +0000 http://rayoflightthemes.com/wordpress-themes/vaxi-wordpress-theme/?p=1833

If you have an android application on google play store you must have received the email that says

“We’ve detected that your app is targeting an old version of Android. To provide users with a safe and secure experience, Google Play requires all apps to meet target API level requirements before Aug 31, 2024”

We are experts at getting the job done. You can contact us to resolve this issue.

The changes that need to be addressed are as follows:

Foreground Service types are required
Choose a foreground service type that represents app’s use case.

    • Camera
    • ConnectedDevice
    • DataSync
    • Health
    • Location
    • MediaPlayback
    • MediaProjection
    • Microphone
    • PhoneCall
    • RemoteMessaging
    • ShortService
    • SpecialUse
    • SystemExempted

“It’s strongly recommended that you migrate to use WorkManager or user-initiated data transfer jobs if a use case of your app isn’t associated with any the types”

Add bluetooth connect permission
This bluetooth method previously required the bluetooth connect permission, but it was not enforced. So declaring Bluetooth connect in your app’s AndroidManifest.xml is essential.

JobScheduler reinforces callback and Network behaviour.
If a job takes too long and exceeds the allowed time on the main thread, the programme generates an app not responding.

“Consider migrating to WorkManager, which provides support for asynchronous processing or migrating any heavy work into a background thread”

JobScheduler also requirement to declare the ACCESS_NETWORK_STATE permission if using setRequiredNetworkType or setRequiredNetwork constraint.

Tiles launch API outdated
If your app launches activities from tiles, use TileService#startActivityAndCollapse(PendingIntent) instead.

Partial access to photos and videos
If you app haven’t used the picture picker yet, incorporating it into your app to provide a uniform experience for selecting images and videos while also improving user privacy without requiring any storage rights.

“If app own gallery picker utilising storage rights and need to keep complete control over it, adjust it to use the new READ_MEDIA_VISUAL_USER_SELECTED permission.”

Secure full-screen Notifications
Apps that are allowed to use full screen notification permission are limited to those that provide calling and alarms only.

A few more slight changes exist. It is mandatory for an Android app to be updated before August 31, 2024. The list is long and time-consuming, but we can check all points and resolve them for you.

]]> https://treeteq.com/your-app-is-affected-by-google-plays-target-api-level-requirements/feed/ 0 Hybrid or Native mobile application for your project https://treeteq.com/hybrid-or-native-mobile-application-for-your-project/ https://treeteq.com/hybrid-or-native-mobile-application-for-your-project/#respond Tue, 02 Jul 2024 14:58:46 +0000 http://rayoflightthemes.com/wordpress-themes/vaxi-wordpress-theme/?p=1830

Every technical person’s first thought is, “Which platform should I use for my mobile application project?”

Several factors can simplify our decision. Hybrid or native?

But first, let’s look at the advantages of hybrid over native and native over hybrid.

Hybrid over Native:

  • Can use a single codebase to run on several platforms, including Windows, MacOS, Android, iOS, and the Web.
  • Quicker time to development
  • Reduced expenses for development and upkeep

Native over Hybrid:

  • Enhanced user interface and improved performance
  • Access to hardware and features unique to a device
  • More safety

Each has their own pros and cons. To make it easier for you to choose, we have listed the differences below.

When to Pick a Hybrid:

  • If you’re on a tight budget or time schedule
  • If using a single codebase to reach a larger audience is your goal
  • If you’re trying to find an easy and affordable fix.

When to Pick a Native:

  • If you wish to offer a top-notch user experience
  • If you require access to hardware and features unique to a device
  • If you’re prepared to spend money on developing each platform separately.

In summary, if you have a limited budget and wish to target multiple platforms without hiring multiple developers or maintaining separate code bases, then go for hybrid. If user experience, security, and device-specific features are important to you, then go for native.

]]> https://treeteq.com/hybrid-or-native-mobile-application-for-your-project/feed/ 0