Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(43)

Solar Industry(8)

User Experience(66)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(18)

Testing(9)

Android(48)

Backend(32)

Dev Ops(11)

Enterprise Solution(29)

Technology Modernization(7)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(38)

Insurtech(66)

Product Innovation(57)

Solutions(22)

E-health(12)

HealthTech(24)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(143)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(19)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

Android N Developer Preview 4

Android N Developer Preview 4 has been recently released. According to the Google, Developer Preview 4 includes the final APIs, which is API level 24. That means apps can now be published with support for API level 24 on Google Play in alpha, beta, and production release channels. Google is also providing the final API to Android Studio 2.1.2 and higher, while also pushing system images to the emulator.Android-N-notifications(1)

New in Developer’s Preview 4

Android N final APIs

Developer Preview 4 includes the final APIs for the upcoming Android N platform. The new API level is 24.

Play publishing

You can now publish apps that use API level 24 to Google Play, in alpha, beta, and production release channels.

Android Studio and tools updates

Along with Developer Preview 4 Google is providing the final API 24 SDK to be used with Android Studio 2.1.2 and higher. In addition, Google is releasing updated Developer Preview 4 system images for the emulator to help test your apps.

As new updates roll out for Android Studio, you should see minor improvements in the new project wizards and AVD manager as we add enhanced support for API 24. These are primarily cosmetic changes and should not stop you from getting your app ready for an update in the Play store.

Here are some of the new feature changes:

  • In previous versions of Android, an app activates with all of its locale resources loaded before locale negotiation begins. Starting in Android N DP4, the system negotiates resource locales individually for each resource object before the app activates.
  • As announced at Developer Preview 3, Google deferred the Launcher Shortcuts feature to a later release of Android. In Developer Preview 4, Google removed the Launcher Shortcuts APIs.
  • Google has changed the BLE Scanning behavior starting in DP4. They have prevented applications from starting and stopping scans more than 5 times in 30 seconds. For long running scans, google will convert them into opportunistic scans.
  • The Multi-Window android:minimalHeight and android:minimalWidth attributes have been renamed to android:minHeight and android:minWidth.gsmarena_000(1)

Known Issues:

  • Stability – Users may encounter system instability (such as kernel panics and crashes).
  • Launcher – The default launcher’s All Apps tray may become unresponsive after cycling the screen off and on. Returning to the homescreen and relaunching the All Apps tray may resolve this issue.
  • Setup Wizard – Crash on selecting “Not now” in “Set up email” screen.
  • Media – Media playback may be unreliable on Nexus 9 and Nexus Player, including issues playing HD video.
    -Occasional freeze when running the YouTube app with other apps in multi-window mode on Pixel C devices. In some cases hard reboot is required.
    -Apps may have issues playing some Widevine DRM-protected content on Nexus 9 devices.
    -Issues handling VP8 video on Nexus 9 devices.
  • External storage – Apps may become unstable when the user moves them from internal storage to adoptable external storage (this can include SD card or devices attached over USB).
  • Screen zoom and multiple APKs in Google Play – On devices running Android N, Google Play services 9.0.83 incorrectly reports the current screen density rather than the stable screen density. When screen zoom is enabled on these devices, this can cause Google Play to select a version of a multi-APK app that’s designed for smaller screens. This issue is fixed in the next version of Google Play services and will be included in a later Developer Preview release.
  • Vulkan support and multiple APKs in Google Play – On devices running Android N, Google Play services 9.0.83 currently reports Vulkan support but not Vulkan version. This can cause Google Play to select a version of a multi-APK app that’s designed for lower Vulkan support on devices with higher version support. Currently, the Google Play Store does not accept uploads of apps which use Vulkan version targeting. This support will be added to the Google Play Store in the future and fixed in the next version of Google Play services (to be included in a later Developer Preview release). Any N devices using the version of Google Play services 9.0.83 will continue to receive versions of apps targeting basic Vulkan support.
  • Accessibility – Switch access doesn’t allow user to navigate web pages in Chrome.
    -Accessibility issues for talkback users with notification dismissal, and wifi selection screen.
  • Android for Work – Currently, CA certificates provisioned through DevicePolicyManager are not available to profiles other than the primary user/profile due to a preload issue. For example, this could prevent a user from connecting to a trusted server when in a Work profile. This issue will be resolved in the next Developer Preview.

 

If you’re a developer and would like to make sure your updated application runs well on Android N, you’ll want to look into using Google Play’s beta testing feature.

Coming in a build number NPD56N, factory images are now available for the Nexus 6P, Nexus 5X, Nexus 6, Nexus 9, Pixel C, Nexus Player, General Mobile 4G (Android One) and the Sony Xperia Z3. Full OTA images are also available, but not for the Z3. If you aren’t keen on updating manually, you can always enroll your device in the Android Beta Program.

For a complete overview of what’s new for users and developers, Approach Mantra Labs at hello@mantralabsglobal.com

Cancel

Knowledge thats worth delivered in your inbox

Why Netflix Broke Itself: Was It Success Rewritten Through Platform Engineering?

By :

Let’s take a trip back in time—2008. Netflix was nothing like the media juggernaut it is today. Back then, they were a DVD-rental-by-mail service trying to go digital. But here’s the kicker: they hit a major pitfall. The internet was booming, and people were binge-watching shows like never before, but Netflix’s infrastructure couldn’t handle the load. Their single, massive system—what techies call a “monolith”—was creaking under pressure. Slow load times and buffering wheels plagued the experience, a nightmare for any platform or app development company trying to scale

That’s when Netflix decided to do something wild—they broke their monolith into smaller pieces. It was microservices, the tech equivalent of turning one giant pizza into bite-sized slices. Instead of one colossal system doing everything from streaming to recommendations, each piece of Netflix’s architecture became a specialist—one service handled streaming, another handled recommendations, another managed user data, and so on.

But microservices alone weren’t enough. What if one slice of pizza burns? Would the rest of the meal be ruined? Netflix wasn’t about to let a burnt crust take down the whole operation. That’s when they introduced the Circuit Breaker Pattern—just like a home electrical circuit that prevents a total blackout when one fuse blows. Their famous Hystrix tool allowed services to fail without taking down the entire platform. 

Fast-forward to today: Netflix isn’t just serving you movie marathons, it’s a digital powerhouse, an icon in platform engineering; it’s deploying new code thousands of times per day without breaking a sweat. They handle 208 million subscribers streaming over 1 billion hours of content every week. Trends in Platform engineering transformed Netflix into an application dev platform with self-service capabilities, supporting app developers and fostering a culture of continuous deployment.

Did Netflix bring order to chaos?

Netflix didn’t just solve its own problem. They blazed the trail for a movement: platform engineering. Now, every company wants a piece of that action. What Netflix did was essentially build an internal platform that developers could innovate without dealing with infrastructure headaches, a dream scenario for any application developer or app development company seeking seamless workflows.

And it’s not just for the big players like Netflix anymore. Across industries, companies are using platform engineering to create Internal Developer Platforms (IDPs)—one-stop shops for mobile application developers to create, test, and deploy apps without waiting on traditional IT. According to Gartner, 80% of organizations will adopt platform engineering by 2025 because it makes everything faster and more efficient, a game-changer for any mobile app developer or development software firm.

All anybody has to do is to make sure the tools are actually connected and working together. To make the most of it. That’s where modern trends like self-service platforms and composable architectures come in. You build, you scale, you innovate.achieving what mobile app dev and web-based development needs And all without breaking a sweat.

Source: getport.io

Is Mantra Labs Redefining Platform Engineering?

We didn’t just learn from Netflix’s playbook; we’re writing our own chapters in platform engineering. One example of this? Our work with one of India’s leading private-sector general insurance companies.

Their existing DevOps system was like Netflix’s old monolith: complex, clunky, and slowing them down. Multiple teams, diverse workflows, and a lack of standardization were crippling their ability to innovate. Worse yet, they were stuck in a ticket-driven approach, which led to reactive fixes rather than proactive growth. Observability gaps meant they were often solving the wrong problems, without any real insight into what was happening under the hood.

That’s where Mantra Labs stepped in. Mantra Labs brought in the pillars of platform engineering:

Standardization: We unified their workflows, creating a single source of truth for teams across the board.

Customization:  Our tailored platform engineering approach addressed the unique demands of their various application development teams.

Traceability: With better observability tools, they could now track their workflows, giving them real-time insights into system health and potential bottlenecks—an essential feature for web and app development and agile software development.

We didn’t just slap a band-aid on the problem; we overhauled their entire infrastructure. By centralizing infrastructure management and removing the ticket-driven chaos, we gave them a self-service platform—where teams could deploy new code without waiting in line. The results? Faster workflows, better adoption of tools, and an infrastructure ready for future growth.

But we didn’t stop there. We solved the critical observability gaps—providing real-time data that helped the insurance giant avoid potential pitfalls before they happened. With our approach, they no longer had to “hope” that things would go right. They could see it happening in real-time which is a major advantage in cross-platform mobile application development and cloud-based web hosting.

The Future of Platform Engineering: What’s Next?

As we look forward, platform engineering will continue to drive innovation, enabling companies to build scalable, resilient systems that adapt to future challenges—whether it’s AI-driven automation or self-healing platforms.

If you’re ready to make the leap into platform engineering, Mantra Labs is here to guide you. Whether you’re aiming for smoother workflows, enhanced observability, or scalable infrastructure, we’ve got the tools and expertise to get you there.

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot