Developer migrates 10 Android apps to API 36 in a weekend, documents every pitfall

·1 views

A developer faced Play Console deadlines requiring all ten of their Android apps to target API 36 by August 31, 2026, and completed the migration in a single weekend. The process involved a mandatory tooling chain upgrade across every project, including bumping Android Gradle Plugin to 8.9.1, Gradle to 8.11.1, and Kotlin to 2.0.21. Seven apps also required an upgrade to Google Play Billing Library 8, which mainly involved adapting to a new callback return type in the product details query API. The migration was complicated by the fact that the ten projects used three different build configurations, meaning version string locations varied constantly across projects. The developer recommends upgrading dependencies in order — SDK, AGP, Gradle, then Kotlin — syncing after each step rather than changing everything at once.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How a Two-Color Design System Keeps Five RAXXO Tools Visually Unified

Developer behind RAXXO built a shared dark UI system across five products — OhNine, Git Dojo, Statusline Builder, Blueprint, and RAXXO Studio — to ensure visual consistency. The system relies on a single charcoal background, two fixed accent colors (cyan and lime), and a strict CSS class prefix 'rx-' to prevent styling conflicts. These rules were not planned from the start but reverse-engineered from the first product and applied forward to every subsequent tool. Limiting the palette to two accents was a deliberate choice to prevent gradual visual drift across products built at different times. The result is a recognizable studio identity without relying on a logo, and a faster, more predictable design process for each new launch.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Rust, Fuzzing, and AI Agents Are Converging to Build Safer Software

Software development is entering an autonomous era where AI agents generate, test, and deploy code at scale, raising new concerns about memory safety and security. Rust's borrow checker addresses many compile-time vulnerabilities by preventing dangling pointers, data races, and memory leaks before code ever runs. However, compile-time guarantees alone are insufficient, as logic errors and vulnerabilities in unsafe code blocks or third-party dependencies can still emerge at runtime. Fuzzing tools like cargo-fuzz and afl.rs complement Rust by bombarding programs with unexpected inputs to surface crashes and memory issues dynamically. Together, Rust's static safety model, corpus-based fuzzing, and AI-assisted code generation are converging to create software ecosystems that are both statically verified and resilient against novel attack vectors.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Knowledge-and-Memory-Management v0.0.2 Adds Portable Paths and Multi-Source Collection

Version 0.0.2 of the Knowledge-and-Memory-Management project has been released as a clean, portable build for developers building agent-based systems. The update replaces all hardcoded personal file paths with a standardized $AGENT_HOME environment variable, making the project deployable across different machines and environments. The release also introduces a knowledge collection feature capable of ingesting content from web pages, videos, and articles. These additions aim to give AI agents a structured, reproducible way to gather and manage external information. The update focuses on foundational portability and data-ingestion groundwork ahead of future memory management enhancements.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Five Common Microservices Mistakes and How to Avoid Them Early

Developers adopting microservices architecture often encounter recurring pitfalls that can undermine the benefits they sought. Key mistakes include decomposing services before understanding domain boundaries, ignoring network reliability, and allowing multiple services to share a single database. Teams also commonly over-engineer orchestration from the start and neglect observability tools like logging, metrics, and distributed tracing. Recommended fixes include starting with a modular monolith, implementing circuit breakers and retries, giving each service ownership of its data, and adopting structured logging with tools such as OpenTelemetry and Prometheus from day one. Experts emphasize that microservices should be treated as a means to an end, with simplicity and observability prioritized throughout.

0 comments Read more at DEV Community