Android Police

Articles Tagged:

bahrain

23

YouTube Premium and Music launch in 8 new countries in the Middle East

Continuing its expansion across the globe, YouTube's paid Premium membership is making its way to my neck of the woods. The service is now available in eight new countries in the Middle East, most of which are in the GCC area. If you live around here, you probably didn't expect Premium to come to us this "soon" after its international launch, so the news is a nice late-night surprise.

Read More
41

[Update: Available for all] Spotify now available in the Middle East and North Africa, if you have an invite

Earlier this year, it was rumored that Spotify would arrive in MENA (Middle East and North Africa) sometime in Q4 2018. It seems the speculation was true, as Spotify has now launched in a handful of MENA countries — but only to those with invites.

Read More
InBrief
19

[Update: Lebanon Too] Paid Google Play Newsstand Content Comes To 8 Middle Eastern Countries

30

Google Play Books Flip Open In 9 Newly-Supported Middle Eastern Countries

On a new Android device (or an old one), opening up the Play Store is the quickest way to get your hands on a digital book. Thing is, that's only the case if you live in a supported country. Today Play Books are making their way to nine countries throughout the Middle East.

Read More
30

Google Maps With Navigation Arrives In Egypt, Saudi Arabia, United Arab Emirates, Jordan And More MENA Countries

While we still wait for newer products like Play Movies or Play Books to reach a wider audience, Google's been hard at work bringing a slightly more useful product to additional countries: Google Maps with Navigation. After bringing voice navigation to India, nine more new countries are being added to the supported list for the Navigation beta. Including the following:

  • Egypt
  • United Arab Emirates
  • Saudi Arabia
  • Qatar
  • Kuwait
  • Lebanon
  • Bahrain
  • Jordan
  • Algeria

nav nav[3]

Unfortunately, the service will require Android 4.0 or higher. This is likely due to Arabic script API incompatibilities with older versions. Though, it's a little unclear on just when all the necessary features would've been added (for example, bi-directional text was only added in Jelly Bean).

Read More