Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(44)

Solar Industry(8)

User Experience(67)

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(8)

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(146)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(21)

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

Lake, Lakehouse, or Warehouse? Picking the Perfect Data Playground

By :

In 1997, the world watched in awe as IBM’s Deep Blue, a machine designed to play chess, defeated world champion Garry Kasparov. This moment wasn’t just a milestone for technology; it was a profound demonstration of data’s potential. Deep Blue analyzed millions of structured moves to anticipate outcomes. But imagine if it had access to unstructured data—Kasparov’s interviews, emotions, and instinctive reactions. Would the game have unfolded differently?

This historic clash mirrors today’s challenge in data architectures: leveraging structured, unstructured, and hybrid data systems to stay ahead. Let’s explore the nuances between Data Warehouses, Data Lakes, and Data Lakehouses—and uncover how they empower organizations to make game-changing decisions.

Deep Blue’s triumph was rooted in its ability to process structured data—moves on the chessboard, sequences of play, and pre-defined rules. Similarly, in the business world, structured data forms the backbone of decision-making. Customer transaction histories, financial ledgers, and inventory records are the “chess moves” of enterprises, neatly organized into rows and columns, ready for analysis. But as businesses grew, so did their need for a system that could not only store this structured data but also transform it into actionable insights efficiently. This need birthed the data warehouse.

Why was Data Warehouse the Best Move on the Board?

Data warehouses act as the strategic command centers for enterprises. By employing a schema-on-write approach, they ensure data is cleaned, validated, and formatted before storage. This guarantees high accuracy and consistency, making them indispensable for industries like finance and healthcare. For instance, global banks rely on data warehouses to calculate real-time risk assessments or detect fraud—a necessity when billions of transactions are processed daily, tools like Amazon Redshift, Snowflake Data Warehouse, and Azure Data Warehouse are vital. Similarly, hospitals use them to streamline patient care by integrating records, billing, and treatment plans into unified dashboards.

The impact is evident: according to a report by Global Market Insights, the global data warehouse market is projected to reach $30.4 billion by 2025, driven by the growing demand for business intelligence and real-time analytics. Yet, much like Deep Blue’s limitations in analyzing Kasparov’s emotional state, data warehouses face challenges when encountering data that doesn’t fit neatly into predefined schemas.

The question remains—what happens when businesses need to explore data outside these structured confines? The next evolution takes us to the flexible and expansive realm of data lakes, designed to embrace unstructured chaos.

The True Depth of Data Lakes 

While structured data lays the foundation for traditional analytics, the modern business environment is far more complex, organizations today recognize the untapped potential in unstructured and semi-structured data. Social media conversations, customer reviews, IoT sensor feeds, audio recordings, and video content—these are the modern equivalents of Kasparov’s instinctive reactions and emotional expressions. They hold valuable insights but exist in forms that defy the rigid schemas of data warehouses.

Data lake is the system designed to embrace this chaos. Unlike warehouses, which demand structure upfront, data lakes operate on a schema-on-read approach, storing raw data in its native format until it’s needed for analysis. This flexibility makes data lakes ideal for capturing unstructured and semi-structured information. For example, Netflix uses data lakes to ingest billions of daily streaming logs, combining semi-structured metadata with unstructured viewing behaviors to deliver hyper-personalized recommendations. Similarly, Tesla stores vast amounts of raw sensor data from its autonomous vehicles in data lakes to train machine learning models.

However, this openness comes with challenges. Without proper governance, data lakes risk devolving into “data swamps,” where valuable insights are buried under poorly cataloged, duplicated, or irrelevant information. Forrester analysts estimate that 60%-73% of enterprise data goes unused for analytics, highlighting the governance gap in traditional lake implementations.

Is the Data Lakehouse the Best of Both Worlds?

This gap gave rise to the data lakehouse, a hybrid approach that marries the flexibility of data lakes with the structure and governance of warehouses. The lakehouse supports both structured and unstructured data, enabling real-time querying for business intelligence (BI) while also accommodating AI/ML workloads. Tools like Databricks Lakehouse and Snowflake Lakehouse integrate features like ACID transactions and unified metadata layers, ensuring data remains clean, compliant, and accessible.

Retailers, for instance, use lakehouses to analyze customer behavior in real time while simultaneously training AI models for predictive recommendations. Streaming services like Disney+ integrate structured subscriber data with unstructured viewing habits, enhancing personalization and engagement. In manufacturing, lakehouses process vast IoT sensor data alongside operational records, predicting maintenance needs and reducing downtime. According to a report by Databricks, organizations implementing lakehouse architectures have achieved up to 40% cost reductions and accelerated insights, proving their value as a future-ready data solution.

As businesses navigate this evolving data ecosystem, the choice between these architectures depends on their unique needs. Below is a comparison table highlighting the key attributes of data warehouses, data lakes, and data lakehouses:

FeatureData WarehouseData LakeData Lakehouse
Data TypeStructuredStructured, Semi-Structured, UnstructuredBoth
Schema ApproachSchema-on-WriteSchema-on-ReadBoth
Query PerformanceOptimized for BISlower; requires specialized toolsHigh performance for both BI and AI
AccessibilityEasy for analysts with SQL toolsRequires technical expertiseAccessible to both analysts and data scientists
Cost EfficiencyHighLowModerate
ScalabilityLimitedHighHigh
GovernanceStrongWeakStrong
Use CasesBI, ComplianceAI/ML, Data ExplorationReal-Time Analytics, Unified Workloads
Best Fit ForFinance, HealthcareMedia, IoT, ResearchRetail, E-commerce, Multi-Industry
Conclusion

The interplay between data warehouses, data lakes, and data lakehouses is a tale of adaptation and convergence. Just as IBM’s Deep Blue showcased the power of structured data but left questions about unstructured insights, businesses today must decide how to harness the vast potential of their data. From tools like Azure Data Lake, Amazon Redshift, and Snowflake Data Warehouse to advanced platforms like Databricks Lakehouse, the possibilities are limitless.

Ultimately, the path forward depends on an organization’s specific goals—whether optimizing BI, exploring AI/ML, or achieving unified analytics. The synergy of data engineering, data analytics, and database activity monitoring ensures that insights are not just generated but are actionable. To accelerate AI transformation journeys for evolving organizations, leveraging cutting-edge platforms like Snowflake combined with deep expertise is crucial.

At Mantra Labs, we specialize in crafting tailored data science and engineering solutions that empower businesses to achieve their analytics goals. Our experience with platforms like Snowflake and our deep domain expertise makes us the ideal partner for driving data-driven innovation and unlocking the next wave of growth for your enterprise.

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot