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 Developers: 3 latest new features in Android

Android_thumb800

Many new updates happened for Android developers lately after Google I/O. Initially there was no restriction on some features but now they have updated them with some restrictions.

We have covered new features and the old features as well with new restrictions.

Here are the old features with new restrictions:

• Background Execution Limits

Whenever an app runs in the background, it consumes some of the device’s limited resources, like RAM. This can result in an impaired user experience, especially if the user is using a resource-intensive app, such as playing a game or watching a video.
To lower the chance of these problems, Android O places limitations on what apps can do while users aren’t directly interacting with them. Apps are restricted in two ways:

Background Service Limitations: When an app’s service is running in the background might consume device resources which may lead to bad user experience, to avoid these type of issues Android system applies a number of limitations on background services, this does not apply to foreground services, which are more noticeable to the user.
Broadcast Limitations: Apps targeted Android O can not use their manifest to register for implicit broadcasts. They can still register for these broadcasts at runtime, and they can use the manifest to register for explicit broadcasts targeted specifically at their app.

Note: The restrictions are applied by default applied to apps which are targeting Android O and in terms of other applications users can enable these restrictions from the Settings screen even if the app has not targeted Android O.

• Android Background Location Limits

Considering battery usage and user experience , background apps which are using Android locations APIs to fetch the user’s location will receive location updates less frequently when the app is being used in a device running Android O, developers who are using Fused Location Provider (FLP), Geofencing, GNSS Measurements, Location Manager, Wi-Fi Manager will get affected by this change.

• Notifications

  1. Notification Badges

    Notification Badges are the new way of notifying users regarding the new notifications arrived for a particular app, this will display badges on app icons in supported launchers which show notifications associated with one or more notification channels in an app, which the user has not yet dismissed or acted on.

  2. Notification Channels

    Using Notification channels developers can group their application’s notifications by category so that the user can apply few characteristics basing on the notification category. When you target Android O, you must implement one or more notification channels to display notifications to your users. If you don’t target Android O, your apps behave the same as they do on Android 7.0 when running on Android O devices.

Google says that the following characteristics can be applied to notification channels and that when the user assigns one of these, it will be applied channel- wide and they are as follows

  • Importance
  • Sound
  • Lights
  • Vibration
  • Show on lock screen
  • Override do not disturb

Here are some new features:

• New in UI and Styling

There are bunch of new features of UI and Styling are introduced in Android O and are as follows

1. Fonts

Android introduced fonts in XML through which we can use custom fonts as resources, You can add your custom font file in res/font/ folder to bundle fonts as resources and can access as a normal resource file and Android Support Library 26 introduce support for APIs to request fonts from a provider application instead of bundling files into your project which helps in reducing your application size
To use these font features on devices running Android API version 14 and higher, a developer needs to use the Support Library 26.

2. Auto Sizing Textviews

By using Support Library 26 Beta developers can now instruct to their app’s Textview to automatically increase or decrease the size to fit perfectly within the boundaries of the Textview.

3. Adaptive Icons

Adaptive icons can display app’s launcher icons in a variety of shapes across different devices for instance in Google Nexus the launcher icon might be in circular and in some Samsung device it might be squircle. Google says that with Android O, each device can provide a mask for the icon, which the OS can use to render all icons with the same shape. This will likely be embraced by OEMs(Original Equipment Manufacturer) who would like to have some unique looking home screens.

4. Autofill Framework

This framework will help the user by pre-filling the user information and user can save time as Filling out forms is a time-consuming and error-prone task. Users can easily get frustrated with apps that require these type of tasks. The Autofill Framework improves the user experience by providing the following benefits:

Less time spent in filling fields Autofill saves users from re-typing information.
Minimize user input errors Typing is prone to errors, especially on mobile devices. Removing the necessity of typing information also removes the errors that come with it.

• Picture in Picture Mode

In Android 7.0, Android TV users can now watch a video in a pinned window in a corner of the screen when navigating within or between apps whereas it was not available to other devices whereas from Android O Picture in Picture is available to all the devices, not just the Android TV.

• Kotlin For Android

Java is the mostly used programming language for the development of Android, When you run a Java application, the app is compiled into a set of instructions called Bytecode and runs in a virtual machine. Many alternative Languages has been introduced to also run on the JVM through which the resulting app looks the same for the JVM
JetBrains, known for IntelliJ IDEA (Android Studio is based on IntelliJ), has introduced the Kotlin language.Kotlin is a statically-typed programming language that runs on the JVM. It can also be compiled to JavaScript source code.

Why Kotlin For Android?

  • Interoperability with Java
  • Intuitive and easy to read
  • Good Android Studio Support
  • Safe to avoid entire classes of errors such as null pointer exceptions.
  • Less to write compared to Java
  • Safe to avoid entire classes of errors such as null pointer exceptions.
  • Versatile for building server-side applications, Android apps or frontend code running in the browser.

Stay tuned for more new updates on Android.

Check out these articles to catch the latest trends in mobile apps:

  1. 7 Important Points To Consider Before Developing A Mobile App
  2. The Clash of Clans: Kotlin Vs. Flutter
  3. Google for India September event 2019 key highlights
  4. Learn Ionic Framework From Scratch in Less Than 15 Minutes!
  5. AI in Mobile Development
  6. 10 Reasons to Learn Swift Programming Language
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