Here come the new Yahoo! Android apps

newsguy 0 640 Views

According to recent reports the Android operating system has an impressive 19.9% share of the US mobile web market. That's still some way behind Apple iOS on 58.8% but the iPhone has been around for a lot longer. It should come as no surprise, then, that Yahoo! wants to get a piece of that Android action. Which is why it has now the continuing expansion of its reach with the immediate availability of Yahoo! Mail and Yahoo! Messenger apps plus a Yahoo! Search Widget for Android.

The new apps come complete with new functionality and enhancements that have been optimised for the Android platform, and are available for OS 2.0 or later from the Android Market as free downloads with immediate effect.

The new Yahoo! Mail Android app enables push notification of new messages, full search of email messages, photos uploading direct from the handset camera or gallery, emoticon and rich text formatting support. Importantly for Yahoo!, it also offers advertisers an opportunity to reach a highly engaged mobile audience and Samsung is the first and inaugural advertiser to take advantage of this. The new Yahoo! Messenger Android app enables sending of instant messages via SMS text message, multitasking with the app working and active in the background, push notifications, plus the same photo and rich formatting support as the Mail app.

The Yahoo! Android search widget is essentially just a one-click route to Yahoo! search, accessible from the Android home screen and complete with voice search, 'Search Assist' for suggestions and recommendations, and an auto-locate technology that delivers locally relevant results. At the moment, the search widget is only available in the US though.

"With the availability of our Yahoo! Mail and Yahoo! Messenger apps for Android" says David Ko, senior vice president, Americas, Audience, Mobile, and Local for Yahoo! "we’re making it easier than ever for consumers to access fast, reliable, and feature-rich Yahoo! experiences across some of the fastest growing platforms in the market."

At the same time, Yahoo! has also upgraded the Yahoo! News service for the iPhone which is now built on HTML5 to give consumers a faster and more sophisticated mobile browsing experience. It includes an all-new layout with animated visual effects and navigation that uses touch gestures. Currently available in the U.S. on the iPhone or iPod Touch browser, the product is expected to become available in additional countries and on additional devices.

android.jpg 8.84 KB

Dani AI

Generated

Good find, . When a large publisher ships native clients it changes the bar for reliability and polish; the practical side for developers is less about features and more about robustness, compatibility, and a clean release pipeline. The checklist below focuses on what to do next, not on the announcement details already in the thread.

  • Compatibility and architecture: pick sensible minSdk/targetSdk, use AndroidX and lifecycle-aware components, and separate UI, domain, and data layers (MVVM or Clean Architecture) so platform changes are easier to absorb.
  • Networking and resilience: use a solid HTTP client with timeouts, caching and exponential backoff; keep UI responsive and surface clear retry/error states.
  • Background work and battery: prefer WorkManager for deferred jobs and foreground services only when necessary; honor Doze and OEM background limits.
  • Permissions and storage: request dangerous permissions at runtime and prefer content URIs/FileProvider or MediaStore access rather than raw file paths.
  • Release hygiene: CI with unit and UI tests, device-matrix testing (including low-end devices), staged rollouts, crash/ANR monitoring, and versioned releases with ProGuard/R8 where appropriate.
  • Privacy and observability: minimal permissions, transparent privacy text, encrypted storage for credentials, and crash/perf telemetry to catch issues early.

A tiny, modern example for letting the system return a picked file (useful for attachments or user content):

private val pickFile = registerForActivityResult(ActivityResultContracts.GetContent()) { uri: Uri? ->
  uri?.let { /* handleUri(it) */ }
}

fun selectFile() {
  pickFile.launch("*/*")
}

Troubleshooting quick wins: reproduce crashes on real devices, use logcat/StrictMode, check OEM-modified firmware for odd behavior, and monitor rollout metrics so fixes can be pushed fast. This set of practices helps keep third‑party competition from becoming a surprise to your users.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview