# apk Published articles for apk. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building a Really, Really Small Android App DevFeed: [Building a Really, Really Small Android App]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-08-22T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [APK](), [Android Studio](), [App](), [Code]() Tags: [android](), [android-studio](), [apk](), [app](), [app-size](), [build](), [engineering](), [mobile](), [news]() ### AI overview This article describes building a minimally viable Khan Academy Android app focused on video playback. The resulting APK was 26 kilobytes to download, supported older Android versions, and offered limited offline navigation. ### Source excerpt By Charlie Marsh App size is important to us. As a team striving to deliver a free, world-class ... Read more ## I Had Never Built A VR App - 8 Days Later, Mine Was On The Quest Store DevFeed: [I Had Never Built A VR App - 8 Days Later, Mine Was On The Quest Store]() Original publisher: [Read original article]() Author: Craig Storm Published: 2026-09-14T15:12:36Z Content type: article Language: en Sources: [UploadVR]() Topics: [ai-coding](), [codex](), [ChatGPT](), [coding](), [Code](), [App](), [Meta](), [APK](), [SDKs]() Tags: [ai](), [ai-coding](), [apk](), [app](), [app-development](), [chatgpt](), [code](), [codex](), [coding](), [meta](), [openxr](), [sdk]() ### AI overview The article describes an eight-day attempt to build and publish Punchable Face, a simple VR game for Meta Quest, despite having little prior development experience. Using Unity, OpenXR, Meta XR SDK components, ChatGPT, and Codex, the project progressed from an empty Unity project through coding, headset testing, store asset creation, submission, and approval on the Meta Quest Store. ### Source excerpt Until a little over a week ago, Craig Storm had never built a VR app. Eight days later, his AI-assisted Quest game Punchable Face was live on Meta's store. ## Watch Follow-Through: Complications, Tiles, and a Companion Wear APK DevFeed: [Watch Follow-Through: Complications, Tiles, and a Companion Wear APK]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [watchOS](), [Android](), [APK](), [App]() Tags: [android](), [apk](), [release](), [watchos]() ### AI overview Codename One now generates watchOS WidgetKit complications, Wear OS complication data sources and Tiles, and a companion Wear APK alongside the phone artifact. The article also explains platform-specific rendering limits and simulator behavior. ### Source excerpt Codename One now generates watchOS WidgetKit complications, Wear OS complication data sources and Tiles, and a companion Wear APK beside the phone artifact. ## Security Week 2635: вредоносное ПО в автомобильных Android-устройствах DevFeed: [Security Week 2635: вредоносное ПО в автомобильных Android-устройствах]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-08-25T08:00:25Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Security](), [Android](), [APK](), [HTTP](), [WebView]() Tags: [2026](), [android](), [apk](), [badbox](), [http](), [security](), [tag-9fe8963de219](), [webview]() ### AI overview Kaspersky researchers discovered Android malware installed on DoFun automotive head units. The JarService dropper downloads a clicker for advertising banners and a reverse-proxy module, linking the campaign to attacks on Android TV set-top boxes and the BADBOX platform. ### Source excerpt Исследователи "Лаборатории Касперского" обнаружили новый Android-зловред, уникальной особенностью которого является установка на головное устройство автомобиля. Вредоносное ПО использовало особенности головных устройств производителя DoFun, позволявшие устанавливать произвольные APK-файлы. Целью распространения вредоносного ПО являлось мошенничество с рекламными баннерами и использование автомобильной магнитолы в качестве прокси-сервера. Исследование кода выявило связи с другими атаками, нацеленными, например, на телеприставки под управлением Android. Расследование началось в июне 2026 года, когда специалисты "Лаборатории Касперского" обнаружили новый дроппер JarService. Зловред устанавливался как обычное пользовательское приложение и никак не маскировался под легитимное ПО. Точнее, у него полностью отсутствовал интерфейс, что указывало на возможность установки без ведома пользователя. Дроппер расшифровывает данные и запускает следующий этап атаки -- вредоносный загрузчик. Он, в свою очередь, отправляет информацию на командный сервер злоумышленников, скачивает оттуда и запускает финальную полезную нагрузку -- кликер на рекламные баннеры и реверс-прокси. Читать далее ## Watch Apps: One Codebase, Two Real Applications DevFeed: [Watch Apps: One Codebase, Two Real Applications]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-22T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [SwiftUI](), [Android](), [media3](), [SQLite](), [API]() Tags: [android](), [api](), [apk](), [apple](), [apple-watch](), [asynchronous](), [files](), [release](), [sqlite](), [state](), [swiftui](), [watchos]() ### AI overview Codename One can build Apple Watch companion applications and Wear OS applications from a shared watch entry point. The article explains separate application runtimes and storage, platform-specific rendering, and asynchronous communication for live messages, replicated state, and file transfers. ### Source excerpt Codename One now builds Apple Watch companions and standalone Wear OS products from one watch entry point, with a portable asynchronous API for messages, state, and files. ## Android Studio Quail 4 Canary 3 now available DevFeed: [Android Studio Quail 4 Canary 3 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-30T14:02:44Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [APK](), [SQLite]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [apk](), [release](), [release-notes](), [sqlite]() ### AI overview Android Studio Quail 4 Canary 3 is available in the Canary channel. The release includes general fixes in Android Studio and Android Gradle Plugin 9.4.0-alpha07, including fixes related to APK parsing and SQLite database inspection. ### Source excerpt Android Studio Quail 4 Canary 3 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 4, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Quail 4, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Quail 4 Canary 3 and Android Gradle Plugin 9.4.0-alpha07. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues APK Viewer Issue #534815916 Bug: IDE fails to parse its own APK, to reach the content of the manifest file Database Inspector Issue #530704637 Launching database inspector segfaults in SQLite ## Apple TV And Android TV: One Codebase, And CSS @media For The Living Room DevFeed: [Apple TV And Android TV: One Codebase, And CSS @media For The Living Room]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [tvOS](), [Android](), [CSS](), [Android APK]() Tags: [android](), [apk](), [apple](), [css](), [ui]() ### AI overview The article describes Codename One support for Apple TV and Android TV from a shared codebase. It covers runtime TV detection, CSS @media styling, Android TV APK generation, and a separate tvOS target built from the same project. ### Source excerpt TV becomes a real form factor: CN.isTV(), runtime device-tv/device-watch CSS @media, an Android TV APK via android.tv, and a tvOS Metal target. ## On-Device Debugging And JUnit 5 DevFeed: [On-Device Debugging And JUnit 5]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-30T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [debugging](), [IntelliJ IDEA](), [Android](), [iOS](), [ide](), [simulator](), [Tooling](), [Code](), [Emulator](), [SDK](), [Visual Studio Code]() Tags: [android](), [android-apps](), [android-studio](), [apk](), [app](), [breakpoint](), [build](), [code](), [debugging](), [developer](), [emulator](), [ide](), [intellij](), [intellij-idea](), [ios](), [java](), [junit](), [linux](), [on-device](), [simulator]() ### AI overview This tutorial describes Codename One's new JDWP-based on-device debugging for ParparVM iOS and Android apps. It explains debugging Java code and objects on simulators and physical devices using IntelliJ IDEA or other JDWP-speaking debuggers, and briefly covers standard JUnit 5 integration with the JavaSE simulator. ### Source excerpt A walk-through of the new JDWP-based on-device debugging pipeline for ParparVM iOS apps and Android apps, with a step-by-step IntelliJ tutorial for each, and a short tutorial on the new standard JUnit 5 integration against the JavaSE simulator. ## Introducing Chainguard OS Packages: Secure ingredients for custom container builds DevFeed: [Introducing Chainguard OS Packages: Secure ingredients for custom container builds]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard os](), [container images](), [Docker Hardened Images](), [Vulnerabilities](), [Linux](), [Automation](), [Dockerfile](), [Open Source](), [bazel](), [chainguard sboms](), [APK]() Tags: [apk](), [apko](), [automation](), [base-images](), [bazel](), [chainguard](), [chainguard-containers](), [chainguard-libraries](), [chainguard-os](), [chainguard-os-packages](), [chainguard-packages](), [chainguard-sboms](), [container](), [container-images](), [cve](), [dockerfiles](), [open-source](), [sboms](), [secure-software-packages](), [software-packages](), [vulnerabilities](), [zero-cve-packages]() ### AI overview Chainguard introduces Chainguard OS Packages, a service providing continuously maintained, enterprise-grade packages and base images for teams that build custom container images. Customers retain control over image composition and build tooling while Chainguard handles package sourcing, rebuilding, vulnerability remediation, and SBOM generation. ### Source excerpt Chainguard OS Packages are enterprise-grade, zero-CVE packages and base images built and continuously maintained in the Chainguard Factory. ## How Chainguard OS Uses Automated Package Garbage Collection to Reduce Security Risk DevFeed: [How Chainguard OS Uses Automated Package Garbage Collection to Reduce Security Risk]() Original publisher: [Read original article]() Published: 2025-12-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard os](), [open-source-security](), [Security](), [APK](), [container images](), [Process]() Tags: [apk](), [automated](), [chainguard-containers](), [chainguard-libraries](), [chainguard-operating-system](), [chainguard-os](), [chainguard-wolfi](), [container-images](), [cves](), [dependency](), [security](), [wolfi]() ### AI overview The article explains how Chainguard automates garbage collection for Chainguard OS and Wolfi APK repositories. It describes filtering older packages and checking dependencies and image usage before removal to keep repositories current and reduce potential attack surface while preserving image customization workflows. ### Source excerpt Learn how we keep Chainguard OS and Wolfi lean and secure with automated package garbage collection that cuts attack surface while preserving reproducibility. ## PostmarketOS demonstrates Gboard integration for Linux mobile keyboards DevFeed: [PostmarketOS demonstrates Gboard integration for Linux mobile keyboards]() Original publisher: [Read original article]() Published: 2025-04-01T00:00:00Z Content type: tutorial Language: en Sources: [postmarketOS Blog]() Topics: [keyboard](), [Mobile](), [Linux](), [Android APK](), [Software](), [Android]() Tags: [android](), [android-apk](), [apk](), [crash](), [environment](), [focus](), [keyboard](), [linux](), [mobile](), [open-source](), [other](), [postmarketos](), [tensorflow](), [training-data]() ### AI overview PostmarketOS demonstrates an experimental keyboard setup in Phosh using Gboard through ATL. The prototype offers suggestions, swiping, autocorrection, and smart input detection, but it crashes often and will not ship because it relies on proprietary software. ### Source excerpt In our previous blog post 2025 Priorities: Reliability, Audio, Cameras and More, we asked "is there anything that you find terribly important that we have missed here?". And indeed, there was one thing that people would have liked us to focus more on, which is a better keyboard experience. This was unbelievably great timing, because we are actually integrating a new keyboard with the following features: Word complete suggestions Swiping Autocorrection of misspelled words Smart detection of what you meant to type vs. which buttons you have actually hit with your fingers We have hooked it up to Phosh, see it for yourself (this is a video, you might need to click it in order to have it start playing): Tech stack Please note that this is in early development. Currently it is still crashing often and you also need to be comfortable running proprietary software since this is actually Gboard running through ATL. So uh... on second thought we will not be shipping this in postmarketOS. However the underlying technology is very much worth showcasing since it allows running components and apps from that other operating system on proper Linux (Mobile) without running a full container! The video is real, and it shows that it is possible to build features like autocorrection and swiping with the APIs we already have in Linux Mobile today. In fact, phosh-osk-stub and swipeGuess can do most of this already! If somebody out there has the interest, skills and time to improve the Linux mobile keyboards to the point that they work as intuitively as proprietary ones: it is possible, get involved! Try it for yourself If you really want to, you can now run this proprietary piece of TensorFlow based software to tap into the results of training data from millions of Android user's keystrokes while tapping with your fingers on your postmarketOS phone. You can also use these instructions with the open source Hacker's Keyboard. Build ATL from sources: sudo apk add -t .atl-builddeps \ libopensles ## Parameterized Android Tests with Burst 2.0 DevFeed: [Parameterized Android Tests with Burst 2.0]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2024-10-31T15:52:32Z Content type: tutorial Language: en Sources: [Handstand Sam]() Topics: [Android](), [Kotlin Multiplatform](), [Kotlin](), [Compiler](), [Test coverage](), [APK](), [Firebase](), [Gradle]() Tags: [analysis](), [android](), [apk](), [firebase](), [gradle](), [instrumentation](), [kotlin](), [kotlin-compiler](), [kotlin-multiplatform](), [updates]() ### AI overview The article explains how Burst 2.0, a Kotlin Compiler Plugin, enables parameterized tests for Kotlin Multiplatform and Android instrumentation tests. It reports that the tests compile and execute successfully from the command line, while noting IDE support issues and a use case for statically computing test names for sharding. ### Source excerpt Parameterized tests allow you to write a test once, but allow it to be called with multiple parameters. This means it is creating more methods than you've written, but without you having to write and maintain each one individually. Here is a trivial example of writing a single test with TestParameterInjector, but having it run [...] ## How to transition to secure container images with new migration guides DevFeed: [How to transition to secure container images with new migration guides]() Original publisher: [Read original article]() Published: 2024-05-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [migration](), [container images](), [container-security](), [APK](), [Dockerfile](), [Package manager](), [Bash](), [Zsh](), [Debian]() Tags: [and-best-practices](), [apk](), [base-images](), [bash](), [best-practices](), [build](), [chainguard](), [chainguard-images](), [container](), [container-based-application](), [container-images](), [container-security](), [container-security-strategy](), [cves](), [debian](), [dependencies](), [docker-hub-image](), [dockerfiles](), [guides](), [how-to](), [image-migration](), [migration](), [migration-guides](), [python-image](), [secure-container-image](), [secure-container-images]() ### AI overview This guide explains how to migrate container images to Chainguard Images for smaller image sizes, fewer vulnerabilities, and continuous maintenance. It covers using -dev images for shells and package managers, installing bash or zsh when needed, searching for packages with apk, and adapting Dockerfiles and entrypoint scripts. ### Source excerpt Struggling to adopt secure container images? Our new migration guides provide step-by-step instructions and best practices for a smooth transition. ## Reimagining the Linux distro with Wolfi DevFeed: [Reimagining the Linux distro with Wolfi]() Original publisher: [Read original article]() Published: 2024-02-21T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Linux](), [chainguard](), [container-security](), [Security](), [Package Management](), [APK](), [Open Source]() Tags: [apk](), [apko](), [chainguard](), [chainguard-images](), [container-security](), [cve](), [linux](), [melange](), [open-source](), [package-management](), [secure-container-images](), [security](), [vulnerabilities](), [wolfi]() ### AI overview The article explains why Chainguard created Wolfi, a minimal Linux distribution designed for modern container use. It describes the roles of Melange for building APK packages and Apko for assembling reproducible container images, along with Wolfi's security advisory and vulnerability-management capabilities. ### Source excerpt Discover Wolfi: Chainguard's answer to modern container security, creating minimal, secure Linux distributions for today's needs. ## Firebase App Distribution Introduces Automated Tester (Beta) DevFeed: [Firebase App Distribution Introduces Automated Tester (Beta)]() Original publisher: [Read original article]() Author: Radhika Advani Published: 2024-02-21T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Smoke Tests](), [Android](), [Testing]() Tags: [android](), [announce](), [apk](), [app-distribution](), [app-quality](), [automated](), [best-practices](), [distribution](), [firebase](), [firebase-cli](), [test-lab]() ### AI overview Firebase App Distribution introduces Automated Tester (Beta), which runs automated smoke tests on Android app builds across selected devices and API levels. Results include reports with screenshots, video recordings, and issues, with Test Lab rates applying after the daily no-cost cap. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Crafting Android bytecode analysis tooling using a secret ingredient (Part 1) DevFeed: [Crafting Android bytecode analysis tooling using a secret ingredient (Part 1)]() Original publisher: [Read original article]() Author: Konstantin Zolotov Published: 2024-02-09T11:50:19Z Content type: tutorial Language: en Sources: [Bumble Tech]() Topics: [Android](), [Tooling](), [APK](), [obfuscation](), [R8](), [Kotlin](), [Java](), [Compiler]() Tags: [andriod-app-development](), [android](), [apk](), [bytecode](), [compilation](), [compiler](), [dagger](), [inlining](), [java](), [kotlin](), [obfuscation](), [optimization](), [r8](), [tooling]() ### AI overview This tutorial introduces Android bytecode analysis through DEX inspection and a tool for examining how source-code changes affect compiled binaries. It explains the Android compilation pipeline from Java or Kotlin source through JVM class files and D8-generated DEX files, then describes R8 obfuscation and optimization, including source maps, tree-shaking, inlining, and outlining. ### Source excerpt During the development process, we often focus on the source code but rarely inspect the compiled bytecode. This means we're missing out on a valuable source of information and data for analysis. How? Let's delve into Dex file inspection and build a tool that demonstrates how source code changes impact the compiled binary. Have you ever set R8 rules to obfuscate your app? Have you used an APK analyzer or a diffuse tool to understand how the code is compiled? Are you confident that debug code hasn't leaked into production? There's another potential pitfall: libraries may provide obfuscation rules (e.g., Gson) that merge with the ones in your project. This means third-party dependencies can alter configurations for the entire app. We often assume everything is fine and that we'll notice if something isn't right. But will we? Does this make you feel uneasy? Does it concern you? Because it certainly concerns me. Here, we'll attempt to enhance the situation and enable you to see precisely how your code changes impact the compiled binary. To better comprehend this, let's start with the code compilation process: It all begins with the Java and/or Kotlin source code, which is then compiled into JVM .class files. Note that at this stage, Java and Kotlin compilers can execute annotation processing tools (APT/KAPT) to generate source code (e.g., Dagger), and Kotlin compiler can run plugins to modify the internal code representation. Then, the D8 compiler takes these compiled classes, third-party libraries (JARs, AARs), and converts them into .dex files. However, if obfuscation and/or minification are enabled (which is almost always the case for release builds), R8 comes into play after D8. R8 obfuscates and optimises the bytecode, and additionally, R8 produces a source map file -- a special file listing all the changes and replacements. Obfuscation replaces human-readable names of various entities (classes, functions, fields, etc.) with very short, yet still unique names, for e ## Images as Code: The pursuit of declarative image builds DevFeed: [Images as Code: The pursuit of declarative image builds]() Original publisher: [Read original article]() Published: 2024-01-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Code](), [chainguard images](), [Dockerfile](), [bazel](), [distroless](), [Docker](), [Containers](), [Kubernetes](), [Terraform](), [Infrastructure as code](), [Open Source]() Tags: [apk](), [apko](), [bazel](), [chainguard](), [chainguard-images](), [code](), [container-image](), [containers](), [declarative](), [distroless](), [docker](), [infrastructure-as-code](), [kubernetes](), [open-source](), [reproducibility](), [terraform]() ### AI overview The article traces the pursuit of declarative container image builds. It critiques imperative Dockerfile-based builds for making multi-tenant, multi-architecture, and reproducible builds difficult, then discusses Bazel and distroless images as steps toward expressing intended build state. Kubernetes and Terraform are presented as examples of declarative systems, inspiring the idea of "Images as Code." ### Source excerpt Chainguard's CTO Matt Moore describes the process of creating a declarative container image build for Chainguard Images. ## Wolfi: a new paradigm in Linux for containers DevFeed: [Wolfi: a new paradigm in Linux for containers]() Original publisher: [Read original article]() Published: 2024-01-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Linux](), [Containers](), [Package Management](), [container images](), [Security]() Tags: [apk](), [apko](), [chainguard](), [chainguard-images](), [containers](), [linux](), [melange](), [package-management](), [security](), [wolfi]() ### AI overview Wolfi is a minimal Linux distribution designed for containerized applications. The article describes its focus on efficiency, security, rapid updates, reproducible APK-based package management, and container image creation through melange and apko. ### Source excerpt Wolfi is a Linux distribution built specifically for containerized applications. See how it can speed up your development process. ## Building minimal, up-to-date cloud images with Wolfi DevFeed: [Building minimal, up-to-date cloud images with Wolfi]() Original publisher: [Read original article]() Published: 2023-12-15T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Cloud](), [container images](), [supply-chain-security](), [Open Source](), [Tooling](), [DevOps]() Tags: [apk](), [apko](), [architecture](), [chainguard-academy](), [cloud](), [common-vulnerabilities-and-exposures](), [container](), [container-images](), [devops](), [efficiency](), [kubecon-na](), [melange](), [minimalism](), [open-source](), [os](), [packages](), [security](), [software-supply-chain-security](), [supply-chain-security](), [vulnerabilities](), [wolfi]() ### AI overview The article introduces Wolfi, an open source project for building minimal, up-to-date cloud and container images. It explains how Wolfi's security-first architecture, proactive updates, minimalism, and supporting tools such as melange, apko, and apk help reduce attack surfaces and CVE exposure while improving software supply chain security. ### Source excerpt Discover Wolfi OS: Crafting minimal, always up-to-date cloud images for superior security and efficiency in the cloud. ## The incremental path to container images: Chainguard Images DevFeed: [The incremental path to container images: Chainguard Images]() Original publisher: [Read original article]() Published: 2023-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [Vulnerabilities](), [Kubernetes](), [vulnerability management](), [Exploit]() Tags: [alpine](), [apk](), [chainguard-images](), [container-image](), [container-images](), [distroless-containers](), [hardened-images](), [helm](), [kubernetes](), [kyverno](), [prometheus](), [sigstore](), [vulnerabilities]() ### AI overview This article explains an incremental approach to migrating existing container images to Chainguard Images. It recommends starting with hardened Application Images that can often be adopted as drop-in replacements, then progressing toward Base Images. ### Source excerpt Explore how easy it is to migrate existing container images to Chainguard Images, whether you are adopting Application Images or Base Images. ## Announcing Bazel rules for extending Chainguard Images DevFeed: [Announcing Bazel rules for extending Chainguard Images]() Original publisher: [Read original article]() Published: 2023-10-24T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [supply-chain-security](), [container images](), [distroless](), [Package manager](), [Open Source]() Tags: [apk](), [apko](), [bazel](), [chainguard](), [chainguard-images](), [distroless](), [sbom](), [secure-software](), [secure-software-supply-chain](), [wolfi]() ### AI overview Chainguard and Aspect.Dev announce the general availability of rules_apko, an open source Bazel plugin for building secure, minimal Wolfi-based OCI container images. The article explains how rules_apko integrates APK packages and Wolfi-base images into existing Bazel workflows, supports reproducible builds, and provides dependency locking, integrity verification, and SBOM generation. ### Source excerpt Explore Bazel rules for Chainguard Images, your pathway to secure, effortless image extension. ## Pokedex UI Testing Series: Getting Started with Maestro in Expo & React Native -- Part 1 DevFeed: [Pokedex UI Testing Series: Getting Started with Maestro in Expo & React Native -- Part 1]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2023-08-19T07:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Expo](), [Testing](), [React Native](), [ui](), [Android](), [iOS](), [APK]() Tags: [android](), [apk](), [ios](), [maestro](), [react-native](), [testing](), [ui-testing]() ### AI overview A guide to setting up local UI testing for an Expo React Native Pokedex app with Maestro on Android and iOS. It covers repository setup, Expo and EAS configuration, development builds, emulator or simulator installation, and a basic Maestro test flow. ### Source excerpt Setup Expo Development builds for Android & iOS ## Get current flavor in Android Gradle DevFeed: [Get current flavor in Android Gradle]() Original publisher: [Read original article]() Author: Ban Markovic Published: 2023-08-07T12:20:20Z Content type: tutorial Language: en Sources: [Stories by Ban Markovic on Medium]() Topics: [Gradle](), [Android](), [Kotlin](), [configuration]() Tags: [android](), [android-app-development](), [androiddev](), [apk](), [assemble](), [configuration](), [gradle](), [groovy](), [kotlin](), [programming]() ### AI overview This tutorial explains how Android product flavors support multiple app variants from one codebase and how to identify the selected flavor in Gradle scripts. It focuses on a Kotlin DSL implementation of a getCurrentFlavor function and mentions a Groovy version. ### Source excerpt Gradle is a topic that most Android developers postpone to learn as much as they can. This happens until we realize that it is a crucial part when it comes to packaging our apps or SDKs (here is my article that can help you out with understanding Gradle better). Since the diversity of Android devices is huge, we always need to strive not to package unnecessary things. Product flavors Sometimes it is required from us to publish different versions of our app, depending on the different requirements of our clients. This leads us to having one codebase that can support multiple configuration changes (enabling or disabling particular features) depending on our clients. To avoid changing our code each time we want to publish a different version of our app, we use product flavors. They enable us to set up different app variants at project level, and then we can reference them in our code, in order to enable or disable something. Problem Enabling or disabling particular features inside our Kotlin code is not that complex, but in order to follow those toggles, sometimes we would also like to include or exclude some plugins or libraries. Since this type of work is done in Gradle, there is a need for us to know which product flavor is selected in our Gradle file. Solution Writing Gradle scripts can be done with Kotlin DSL or Groovy, and since we already know Kotlin, I will focus on explaining the Kotlin DSL solution and later on I will also provide the full Groovy version of our getCurrentFlavor function. By using Kotlin DSL in our Gradle scripts, we can add any function at the bottom of our app/build.gradle.kts file, so let's create our getCurrentFlavor() function that returns an empty String. fun getCurrentFlavor(): String { return "" } Since we are inside our build.gradle.kts file, we have a reference to a Gradle object that belongs to our project. Inside it, we have the information of the parameters that the Gradle object uses for starting the build. By having that informa ## Keeping Up with Android App Size Growth DevFeed: [Keeping Up with Android App Size Growth]() Original publisher: [Read original article]() Author: Justin Wong Published: 2023-06-27T06:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [LineageOS](), [APK](), [ci](), [Mobile](), [Development]() Tags: [android](), [android-app-bundle](), [android-studio](), [apk](), [app-size](), [build](), [ci](), [development](), [engineering](), [google-play](), [libraries](), [mobile-apps](), [pipeline](), [script]() ### AI overview Square describes how it manages Android app size growth across a monorepo by applying size-reduction techniques, tracking changes in continuous integration, and improving team accountability. The post also covers automation and tools for identifying savings and comparing APK versions. ### Source excerpt Tracking app size changes in CI and ensuring team accountability [Next page]()