# build times Published articles for build times. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Linux 7.4 Could End Up Seeing Kernel Builds ~36% Faster, Incremental Builds ~70% Faster DevFeed: [Linux 7.4 Could End Up Seeing Kernel Builds ~36% Faster, Incremental Builds ~70% Faster]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T10:31:16Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [build performance](), [build times](), [Arm](), [Compiler](), [Git](), [Artificial Intelligence]() Tags: [ai](), [arm](), [build-times](), [compiler](), [desktop-linux](), [git](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview A second revision of Linux kernel patches could make full allmodconfig builds about 36% faster and incremental builds about 70% faster. The work, led by Lorenzo Stoakes of Arm, addresses single-threaded bottlenecks and includes fixes, an upstream rebase, and an optional parallel Rust compiler front end. The patches are being considered for inclusion in Linux 7.4. ### Source excerpt Earlier this month I wrote about a patch series posted to the Linux kernel mailing list that addressed a lot of "hideous code" to make Linux kernel builds faster. A number of single-threaded bottlenecks were tracked down and fixed within the Linux kernel thanks to the assistance of AI. A second revision of those patches hit the mailing list this morning and there is hope they could be upstreamed for Linux 7.4... ## Starlight 0.42 DevFeed: [Starlight 0.42]() Original publisher: [Read original article]() Author: Chris Swithinbank Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [The Astro Blog]() Topics: [releases](), [Accessibility](), [build times](), [Command-line interface](), [changelog]() Tags: [accessibility](), [astro](), [build-times](), [changelog](), [cli](), [javascript](), [release](), [typescript]() ### AI overview Starlight 0.42 reduces client-side JavaScript through the Popover API, compiles its published source to JavaScript with type definitions, and includes build-time and accessibility improvements. ### Source excerpt Less JavaScript, and more JavaScript, all in one release. ## Clearer Build Optimization Results with GitHub Copilot DevFeed: [Clearer Build Optimization Results with GitHub Copilot]() Original publisher: [Read original article]() Author: David Li Published: 2026-08-13T18:18:50Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [GitHub Copilot](), [Optimization](), [build performance](), [build times](), [C++](), [Windows](), [Visual Studio 2026]() Tags: [build-insights](), [build-optimization](), [build-performance](), [build-times](), [c-plus-plus](), [github-copilot](), [optimization](), [performance](), [visual-studio](), [visual-studio-2026](), [windows](), [workflow]() ### AI overview GitHub Copilot build performance for Windows now provides deterministic messages for optimization outcomes, including successful improvements, changes below the success threshold, unsuccessful changes, and builds that were too short to analyze. Successful results include baseline and final build times, measured improvement, and effects on iterative builds when applicable. ### Source excerpt We know that slow builds are a consistent theme in feedback from C++ developers. Your feedback helped us to shape GitHub Copilot build performance for Windows, an agent that can trace your build, find bottlenecks, apply optimizations, and measure the result. When using the agent, the clearest outcome is a straightforward win. The agent changes [...] The post Clearer Build Optimization Results with GitHub Copilot appeared first on C++ Team Blog. ## What's new in Astro - July 2026 DevFeed: [What's new in Astro - July 2026]() Original publisher: [Read original article]() Author: Sarah Rainsberger Published: 2026-07-31T00:00:00Z Content type: news Language: en Sources: [The Astro Blog]() Topics: [releases](), [GSAP](), [build times]() Tags: [agentic](), [astro](), [benchmark](), [build-times](), [gsap](), [releases](), [webflow]() ### AI overview A July Astro ecosystem roundup covering Astro 7.1 updates, community events, a Webflow and CodeTV hackathon using GSAP, and selected community content. ### Source excerpt July 2026 - CodeTV GSAP Webflow contest, Astro Germany, and more! ## Faster C++ iterative builds with GitHub Copilot DevFeed: [Faster C++ iterative builds with GitHub Copilot]() Original publisher: [Read original article]() Author: David Li Published: 2026-07-17T14:22:57Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [build times](), [C++](), [AI Bots]() Tags: [agent](), [build-insights](), [build-optimization](), [build-performance](), [build-times](), [c-plus-plus](), [copilot](), [diagnostics](), [game-development](), [github](), [github-copilot](), [optimization](), [performance](), [tool](), [visual-studio](), [visual-studio-2026](), [windows](), [workflow]() ### AI overview GitHub Copilot build performance for Windows adds an iterative build tool that evaluates optimization changes against incremental builds as well as clean builds. ### Source excerpt Slow builds are a consistent theme of feedback from C++ developers. We built GitHub Copilot build performance for Windows so you can leverage Copilot to optimize your project's build times. This workflow will find optimizations that bring your build times down. At first, we only measured the impact of build optimizations on full clean builds. [...] The post Faster C++ iterative builds with GitHub Copilot appeared first on C++ Team Blog. ## A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage DevFeed: [A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-07-15T13:38:11Z Content type: article Language: en Sources: [Blogs on Ryan Harter]() Topics: [Gradle](), [build times](), [modules](), [test-coverage](), [Android Gradle Plugin](), [Kotlin]() Tags: [android-gradle-plugin](), [build](), [build-times](), [gradle](), [kotlin](), [modules](), [test-coverage]() ### AI overview The article describes a Gradle module convention that separates each feature's public API from its implementation. The author says this structure reduced build times and coupling between features while helping enforce test coverage, with Android Gradle Plugin support making a separate test-fixtures module unnecessary. ### Source excerpt Flattening my Dependency Graph Jesse Wilson Jesse explores a Gradle module structure that he likes. Read now ➡ I liked this not-so-recent post from Jesse Wilson, which outlines a Gradle module convention that prioritizes clear public/private boundaries to support encapsulation and build speed. The approach, adapted from one presented by Ralf Wondratschek, also happens to closely resemble one that I helped institute at Dropbox shortly after I joined four and a half years ago. ## Turbopack: What's New in Next.js 16.3 DevFeed: [Turbopack: What's New in Next.js 16.3]() Original publisher: [Read original article]() Author: Andrew Imm Published: 2026-06-29T20:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Cache](), [Caching](), [build times](), [Compiler](), [Persistence](), [Rust](), [cpu]() Tags: [build-times](), [cache](), [caching](), [cpu](), [development](), [memory](), [next-js](), [performance](), [persistence](), [rust]() ### AI overview Next.js 16.3 improves the Turbopack bundler with lower development memory usage, persistent filesystem caching for faster builds, experimental Rust React Compiler support, API support, and faster hot module replacement and development startup. Memory-cache eviction, enabled by default with the development filesystem cache, helps prevent unbounded memory growth during long development sessions. ### Source excerpt Turbopack in Next.js 16.3 adds development memory eviction, persistent file cache for builds, experimental Rust React Compiler, and `import.meta.glob` support. ## Announcing TypeScript 7.0 RC DevFeed: [Announcing TypeScript 7.0 RC]() Original publisher: [Read original article]() Author: Daniel Rosenwasser Published: 2026-06-18T14:31:17Z Content type: release Language: en Sources: [TypeScript]() Topics: [TypeScript](), [Go Language](), [Compiler](), [build times](), [npm](), [vs-code](), [Extension](), [ci]() Tags: [build-times](), [ci](), [development](), [extension](), [go](), [performance](), [post](), [release](), [speed](), [typescript](), [vs-code]() ### AI overview TypeScript 7.0 RC introduces a Go-based compiler foundation with shared-memory parallelism, reporting substantial speed improvements while preserving TypeScript 6.0's type-checking semantics. The release candidate is available through npm, with an optional VS Code preview extension for faster editing. ### Source excerpt Today we are excited to announce the Release Candidate of TypeScript 7.0! If you haven't been following TypeScript 7.0's development, this release is significant in that it is built on a completely new foundation. Over the past year, we have been porting the existing TypeScript codebase from TypeScript (as a bootstrapped codebase that compiles to [...] The post Announcing TypeScript 7.0 RC appeared first on TypeScript. ## Optimizing Our Build Times by Migrating from Webpack to Rspack DevFeed: [Optimizing Our Build Times by Migrating from Webpack to Rspack]() Original publisher: [Read original article]() Author: Benson Pan, Software Engineer Published: 2026-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Yelp]() Topics: [Webpack](), [build times](), [monorepo](), [build performance](), [Developer experience]() Tags: [build](), [build-times](), [build-tools](), [developer-experience](), [migration-guide](), [monorepo](), [performance](), [speed](), [tooling](), [tools](), [webpack]() ### AI overview A Yelp engineering blog post explains how the team migrated monorepo builds from Webpack to Rspack. It reports an approximately 50% reduction in build time and discusses compatibility, configuration, custom plugins, and a staged rollout. ### Source excerpt Over the years, Webpack has remained the bundler of choice for many JS projects, including here at Yelp. While it has served us well, its speed has increasingly become a bottleneck as our monorepo continues to grow. Fortunately, a bunch of new build tools (Vite, Parcel, Rspack, etc.) have emerged in recent years. Each of these tools promises different ways of improving performance and developer experience. In this blog post, we'll walk through how we migrated our monorepo builds from Webpack to Rspack and achieved an approximately 50% reduction in build time. Why Rspack Our team has been closely observing... ## Metro 1.0.0 Is Stable as a Kotlin Multiplatform Compile-Time Dependency Injection Framework DevFeed: [Metro 1.0.0 Is Stable as a Kotlin Multiplatform Compile-Time Dependency Injection Framework]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-04-27T21:07:22Z Content type: release Language: en Sources: [Zac Sweers]() Topics: [Kotlin](), [Dependency injection](), [multiplatform](), [Compiler](), [Framework](), [gradle-plugin]() Tags: [build-performance](), [build-times](), [compilation](), [compiler](), [dependency-injection](), [experimental](), [gradle](), [gradle-plugin](), [incremental](), [kotlin](), [metro](), [multiplatform](), [open-source](), [perfetto](), [stable]() ### AI overview Metro 1.0.0 is now stable. The Kotlin multiplatform compile-time dependency injection framework uses a compiler plugin and provides API-stable runtime APIs, MetroX artifacts, and a Gradle plugin unless marked experimental. The article also describes build-performance improvements and compile-time validation features. ### Source excerpt New here? Metro is a multiplatform, compile-time dependency injection framework for Kotlin implemented as a compiler plugin. Metro 1.0.0 is out now and stable. This means that its runtime APIs (runtime, MetroX artifacts, Gradle plugin, etc.) are now API-stable unless annotated with an experimental annotation. This ## Announcing TypeScript 7.0 Beta DevFeed: [Announcing TypeScript 7.0 Beta]() Original publisher: [Read original article]() Author: Daniel Rosenwasser Published: 2026-04-21T18:24:17Z Content type: release Language: en Sources: [TypeScript]() Topics: [build times](), [ci]() Tags: [build-times](), [ci](), [command-line](), [extension](), [go](), [javascript](), [release](), [speed](), [typescript](), [vs-code]() ### AI overview TypeScript 7.0 Beta introduces a Go-based compiler foundation that the article says is often about ten times faster than TypeScript 6.0 while preserving its type-checking semantics. It is presented as ready for day-to-day use, CI pipelines, and VS Code editing through a preview extension. ### Source excerpt Today we are absolutely thrilled to announce the release of TypeScript 7.0 Beta! If you haven't been following TypeScript 7.0's development, this release is significant in that it is built on a completely new foundation. Over the past year, we have been porting the existing TypeScript codebase from TypeScript (as a bootstrapped codebase that compiles [...] The post Announcing TypeScript 7.0 Beta appeared first on TypeScript. ## App Hosting has in-console environment variables and faster builds DevFeed: [App Hosting has in-console environment variables and faster builds]() Original publisher: [Read original article]() Author: Julia Reid Published: 2026-03-12T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [hosting](), [build performance](), [configuration](), [Deployment]() Tags: [app-hosting](), [build-times](), [cloud-native](), [configuration](), [deployment](), [environment-variables](), [firebase](), [firebase-console](), [javascript](), [web]() ### AI overview Firebase App Hosting now supports adding and editing environment variables in the Firebase console. The update also describes configuration merging, precedence rules, secret references, and an optimized build process intended to improve build times. ### Source excerpt Manage environment variables in the Firebase console, and learn about a small change our engineering team made to improve build times for everyone. ## Why I'm Seeking Sponsors for Metro, a Kotlin Dependency Injection Compiler DevFeed: [Why I'm Seeking Sponsors for Metro, a Kotlin Dependency Injection Compiler]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-01-29T15:56:29Z Content type: opinion Language: en Sources: [Zac Sweers]() Topics: [Compiler](), [Dependency injection](), [build performance](), [build times](), [Kotlin](), [Mobile](), [monorepo]() Tags: [android](), [build-performance](), [build-times](), [compiler](), [dependency-injection](), [developer-productivity](), [kotlin](), [metro](), [monorepo](), [open-source]() ### AI overview The author discusses opening GitHub sponsorship for Metro, a Kotlin dependency injection project. They report build-performance gains, benchmark results against Dagger, compatibility across Kotlin and IDE versions, and adoption by several engineering teams. ### Source excerpt Metro is the proudest work of my career. Ever since starting it on vacation in November 2024, building it has been an incredible journey and the community reception has been nothing short of wonderful. It sits at the intersection of several fields I've come to specialize in, ranging ## Optimizing Docker Image Builds for Size and Build Time DevFeed: [Optimizing Docker Image Builds for Size and Build Time]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2025-07-31T17:25:43Z Content type: tutorial Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Docker](), [Docker Image](), [Dockerfile](), [build performance](), [build times](), [Benchmark](), [Go Language]() Tags: [alpine](), [benchmark](), [build-performance](), [build-times](), [docker](), [docker-image](), [docker-image-size](), [go](), [how-to]() ### AI overview This tutorial describes optimizing a Go backend Docker image using Alpine base images and multi-stage builds. The reported changes reduced image size from 1.29 GB to 27.1 MB and build time from 43.8 seconds to 23.6 seconds. ### Source excerpt How to optimize (and benchmark) docker image builds for build time and image size. ## How Blacksmith paired Postgres and ClickHouse for fast CI and real-time observability DevFeed: [How Blacksmith paired Postgres and ClickHouse for fast CI and real-time observability]() Original publisher: [Read original article]() Author: ClickHouse Published: 2025-07-29T12:50:25Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [ci](), [telemetry](), [build times](), [GitHub Actions]() Tags: [analytics](), [build-times](), [ci](), [clickhouse](), [cloud](), [github-actions](), [observability](), [postgres](), [real-time]() ### AI overview Blacksmith uses Postgres for operational metadata and ClickHouse Cloud to query large volumes of CI observability data. The article describes the move as a way to improve analytical-query performance, scalability, and developer experience. ### Source excerpt What happens when you combine Postgres, ClickHouse Cloud, and real-time ingestion via the Postgres CDC connector in ClickPipes? ## The quest for the five minute deploy DevFeed: [The quest for the five minute deploy]() Original publisher: [Read original article]() Author: Matthew Barrington Published: 2025-07-22T10:07:34Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [CI/CD](), [build times](), [Caching](), [Go Language](), [Deployment]() Tags: [build-times](), [caching](), [ci-cd](), [deployment](), [go](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [slack-incident](), [speed]() ### AI overview This article describes how incident.io worked to reduce deployment time toward a goal of less than five minutes from merging a pull request to production. It examines slow Go builds and test suites, limitations of CI/CD caching, and the decision to evaluate different CI/CD providers based on price, reliability, extensibility, and familiarity. ### Source excerpt This is the story of how incident.io drastically cut down their code deployment times, detailing their journey from slow, inefficient CI/CD pipelines to achieving near "five-minute deploys" through strategic changes to their infrastructure and caching mechanisms. ## Analyze Your Nx Cloud Runs With Your AI Assistant DevFeed: [Analyze Your Nx Cloud Runs With Your AI Assistant]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2025-06-25T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [ci](), [Model Context Protocol (MCP)](), [Cloud APIs](), [Conversational AI](), [Architecture & optimization](), [build times]() Tags: [ai](), [ai-assistants](), [build-times](), [ci](), [devops](), [mcp](), [model-context-protocol-mcp](), [nx](), [nx-cloud](), [optimization](), [resource]() ### AI overview This article explains how Nx Cloud MCP connects AI assistants to live CI data so technical teams can analyze pipeline runs conversationally, identify recurring build and test failures, compare cache performance, and optimize development workflows. ### Source excerpt Learn how to use Nx Cloud MCP to analyze CI data conversationally with AI assistants, identify failure patterns, and optimize your development pipeline through data-driven insights. ## Building Scalable Mobile Projects at Android Makers 2025 DevFeed: [Building Scalable Mobile Projects at Android Makers 2025]() Original publisher: [Read original article]() Author: Cyril Mottier Published: 2025-04-10T08:37:01Z Content type: opinion Language: en Sources: [Cyril Mottier Blog]() Topics: [Mobile](), [scaling](), [builds](), [build times](), [maintenance]() Tags: [2025](), [build-times](), [builds](), [maintenance](), [mobile](), [scaling]() ### AI overview The article introduces a keynote on scaling mobile projects as codebases, contributor counts, and complexity grow. It highlights strategies for maintaining fast build times, reusable code, clear ownership, and resilient project structure. ### Source excerpt Edit - Aug 4: adding link to the video on YouTube I recently gave a keynote called "Building Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership" at Android Makers 2025 in Paris. Here was the abstract. Every successful project eventually faces the challenges of scaling: an ever-growing codebase, an increasing number of contributors, and rising complexity. Without proper measures, this can lead to slow build times, a cluttered codebase, maintenance difficulties, code duplication, and even dead code--ultimately jeopardizing the company's ability to deliver value. ## Next.js 15.3 DevFeed: [Next.js 15.3]() Original publisher: [Read original article]() Author: Will Binns-Smith Published: 2025-04-09T20:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [build performance](), [Instrumentation](), [Routing (disambiguation)](), [Caching](), [Webpack](), [Vercel]() Tags: [build-performance](), [build-times](), [caching](), [experimental](), [instrumentation](), [next-js](), [routing](), [typescript](), [vercel](), [webpack]() ### AI overview Next.js 15.3 introduces alpha support for Turbopack production builds, alongside client instrumentation and navigation hooks. The release also includes experimental Rspack community support and TypeScript plugin improvements. Turbopack is reported to outperform Webpack as CPU cores increase, while persistent caching remains experimental. ### Source excerpt Next.js 15.3 includes Turbopack for builds, new client instrumentation and navigation hooks, and more. ## Nuxt UI v3 DevFeed: [Nuxt UI v3]() Original publisher: [Read original article]() Published: 2025-03-12T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [Vue.js](), [Accessibility](), [Tailwind CSS](), [User interface design](), [modern web development]() Tags: [accessibility](), [build-times](), [css](), [dark-mode](), [guide](), [nuxt](), [performance](), [release](), [tailwind](), [vue]() ### AI overview Nuxt UI v3 is a major redesign of the UI library for Vue and Nuxt developers. It adds accessibility features such as keyboard navigation, automatic ARIA attributes, focus management, and screen-reader-friendly components. Tailwind CSS v4 integration improves rendering, build times, and bundle efficiency, while semantic color tokens simplify theming and light/dark mode support. Nuxt UI and Nuxt UI Pro are also described as compatible with Vue projects outside Nuxt. ### Source excerpt Nuxt UI v3 is out! After 1500+ commits, this major redesign brings improved accessibility, Tailwind CSS v4 support, and full Vue compatibility ## Astro 5.3 DevFeed: [Astro 5.3]() Original publisher: [Read original article]() Author: Matt Kane Published: 2025-02-13T00:00:00Z Content type: release Language: en Sources: [The Astro Blog]() Topics: [Astro](), [build times](), [Server-side rendering](), [Netlify]() Tags: [astro](), [benchmark](), [build](), [build-times](), [cli](), [community-contribution](), [experimental](), [netlify](), [ssr]() ### AI overview Astro 5.3 improves page-rendering performance by avoiding unnecessary asynchronous rendering, with reported gains for SSR responses and static build times. It also adds automatic session storage setup for supported adapters, more control over Netlify bundling, and improved request handling. ### Source excerpt Astro 5.3 is here with faster page rendering, easier setup for experimental sessions, and more! ## Wise Tech Stack (2025 update) DevFeed: [Wise Tech Stack (2025 update)]() Original publisher: [Read original article]() Author: Milon James Published: 2025-02-12T13:34:08Z Content type: article Language: en Sources: [Wise Engineering - Medium]() Topics: [Development](), [Mobile](), [Web](), [Tuist](), [Storybook](), [Testing](), [build performance]() Tags: [build-times](), [caching](), [data](), [engineering](), [mobile](), [next-js](), [platform](), [storybook](), [swift](), [swift-package-manager](), [tech](), [tech-stack](), [testing](), [tuist](), [update](), [web](), [xcode](), [xcodegen]() ### AI overview Wise's 2025 technology update describes its web, iOS, and Android engineering stack, including Next.js-based web applications, Storybook visual testing, migration from Xcodegen to Tuist, adoption of Swift Package Manager, and Android development across a large Gradle repository. ### Source excerpt Wise Engineering As of the financial year 2025, Wise supports 15.6 million active customers, moving approximately GBP 36 billion across borders each quarter. Approximately 65% of our transfers arrive instantly, and our Wise Platform facilitates payments for banks, financial institutions and enterprises globally. This success is driven by our technology-first approach, robust architecture, and dedicated engineering teams. Photo by Randy Fath on UnsplashHow we work at Wise Wise has more than 850 engineers working across key global locations, organised into independent squads and tribes. These teams are empowered to innovate and make decisions independently, fostering transparency, trust, and collaboration. This article follows our Tech Stack 2022 to cover the most recent improvements in Wise's tech stack that enable us to achieve our mission of money without borders -- instant, convenient, transparent and eventually free. Moving money with WiseOur web and mobile applications Our web applications are built using CRAB (a Wise-specific abstraction on top of the popular Next.js framework) and comprises of 40 distinct apps, each handling specific product functions making deployments safer and more manageable. One of the biggest changes has been in our testing methodology. We've adopted Storybook for visualising individual React components during development. Storybook pairs really well with Chromatic which captures snapshots after each change and can highlight the visual differences in the component. These snapshots are very effective for catching visual regressions during code changes which helps us prevent bugs from reaching our customers. Wise mobile app: faster, smarter, and more efficient Our iOS engineers have upgraded our infrastructure by migrating 250+ Xcode modules from Xcodegen to Tuist and switching from Cocoapods to Swift Package Manager (SPM), unlocking improvements in caching for builds. The team also improved flexibility, reducing zero-change build times from 2 ## The Ultimate Guide to Developing High-Quality Android Libraries DevFeed: [The Ultimate Guide to Developing High-Quality Android Libraries]() Original publisher: [Read original article]() Author: Akshay Bora Published: 2024-12-04T08:27:06Z Content type: tutorial Language: en Sources: [Android@Microsoft - Medium]() Topics: [Android Library](), [Library](), [Development](), [API](), [Testing](), [Developer experience]() Tags: [android](), [api](), [build-times](), [consistency](), [documentation](), [error-handling](), [guide](), [libraries](), [library-design](), [mobile](), [quality](), [ui-testing]() ### AI overview A practical guide to developing high-quality Android libraries. It recommends using a dedicated playground or development app for isolated feature development, shorter build times, UI testing, easier replacement of implementations, and better integration references. It also advises maintaining a simple, consistent, well-documented, encapsulated API with graceful error handling. ### Source excerpt In the fast-paced world of software development, creating Libraries efficiently and effectively is crucial to ensure the code reuse across apps. Here are some preferred practices to help you streamline your Library development process and guide you towards unlocking the secrets of building a top-notch Android Library. In Microsoft we do use these guidelines while developing the Libraries like File Picker, Share and Calendar libraries which helped us big time. 1. Create a Playground/Development App When developing libraries, it is advantageous to create a playground or development application that integrates with the library for faster development cycles. This approach has proven highly beneficial, as developers no longer need to build an example Teams codebase to test the libraries, significantly reducing the time required for testing. This approach offers several benefits: Isolated Testing: Developers can test and develop features in isolation, without waiting for integration into the consumer codebase. This leads to faster development cycles. Shorter Build Times: The development app targets specific features, resulting in quicker builds. Developers can launch the feature they want to test with just a click. UI Testing: Run UI tests from the playground app, allowing the consumer or library to focus on integration tests. Feature-level UI tests can be handled in isolation. Easier Replacement: Replace actual implementations with fake ones for UI tests easily. Better Integration References: Provide better integration references in developer documentation and stakeholders to play around before consuming the Library. 2. Cleaner API Surface When developing high-quality Android libraries, it's crucial to maintain a clean and intuitive API surface. A cleaner API surface ensures that your library is easy to understand and use, which can significantly enhance the developer experience. Simplicity: Keep your API simple and avoid unnecessary complexity. Provide clear, concise me ## What We Learned Migrating From Webpack to Vite DevFeed: [What We Learned Migrating From Webpack to Vite]() Original publisher: [Read original article]() Author: Roman Zaynetdinov Published: 2024-11-20T17:59:21Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Web Development](), [web applications]() Tags: [api](), [build-times](), [engineering](), [go](), [javascript](), [migration](), [tooling]() ### AI overview Neon describes migrating its SPA build system from Webpack to Vite. The migration targeted faster builds, hot module replacement, fewer dependencies, and integration with a Go backend that renders HTML and injects user properties. ### Source excerpt The Neon Console is a Single Page Application (SPA), or rather, a collection of SPAs. Static assets like JavaScript and CSS are served through CloudFront, while the HTML is dynamically rendered by our Go backend. In this post, we'll dive into our journey of migrating from webpack... [Next page]()