# APK APK is an Android package archive file containing an app's runtime contents, used by Android devices to install the app. 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. Зловред устанавливался как обычное пользовательское приложение и никак не маскировался под легитимное ПО. Точнее, у него полностью отсутствовал интерфейс, что указывало на возможность установки без ведома пользователя. Дроппер расшифровывает данные и запускает следующий этап атаки -- вредоносный загрузчик. Он, в свою очередь, отправляет информацию на командный сервер злоумышленников, скачивает оттуда и запускает финальную полезную нагрузку -- кликер на рекламные баннеры и реверс-прокси. Читать далее ## 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 ## BTMOB: A stealthy RAT burrowing deep into Android devices DevFeed: [BTMOB: A stealthy RAT burrowing deep into Android devices]() Original publisher: [Read original article]() Author: Daniel Cunha Barbosa Published: 2026-05-26T08:50:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [ransomware](), [Remote Access Trojan](), [Android](), [Social engineering](), [APK](), [Tooling](), [Accessibility]() Tags: [android](), [code](), [malware](), [phishing](), [remote-access-trojan](), [social-engineering](), [tool]() ### AI overview BTMOB is an Android remote access trojan that spreads through phishing websites, fake app stores, and malicious APKs. It can exfiltrate sensitive data, capture screenshots, record device activity, and enable remote control. Its APK builder and malware-as-a-service model make customized campaigns easier to launch. ### Source excerpt The malware pairs remote access capabilities with ready-made campaign tools, lowering the barrier for full device compromise ## Chainguard brings first-party RHEL 9 and RHEL 10 RPM support to Chainguard OS, joins FINOS DevFeed: [Chainguard brings first-party RHEL 9 and RHEL 10 RPM support to Chainguard OS, joins FINOS]() Original publisher: [Read original article]() Published: 2026-05-11T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard os](), [chainguard containers](), [Security](), [Critical Infrastructure](), [Package Management](), [Open Source](), [Cloud Native Ecosystem](), [Resilience](), [APK](), [Linux]() Tags: [chainguard](), [chainguard-containers](), [chainguard-finserv](), [chainguard-os](), [cloud](), [cloud-native](), [compatibility](), [compliance](), [container](), [container-images](), [containers](), [critical-infrastructure](), [cve](), [dependencies](), [hardening](), [images](), [linux](), [make](), [mythos](), [open](), [open-source](), [project-glasswing](), [rhel](), [rhel-10](), [rhel-9]() ### AI overview Chainguard announces first-party RHEL 9 and RHEL 10 RPM compatibility for packages in Chainguard Containers built on Chainguard OS. The company also announces that it is joining FINOS to support open source collaboration in financial infrastructure. ### Source excerpt Chainguard adds first-party RHEL 9/10 RPM compatibility and joins FINOS, helping financial institutions modernize securely for the AI-driven threat era. ## 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. ## Custom Assembly and Private APK Repositories are Now Generally Available DevFeed: [Custom Assembly and Private APK Repositories are Now Generally Available]() Original publisher: [Read original article]() Published: 2025-07-15T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard containers](), [APK](), [container images](), [Security]() Tags: [announce](), [apk-repositories](), [chainguard-containers](), [container-images](), [custom-assembly](), [cve-remediation](), [new-features](), [secure-image](), [slsa]() ### AI overview Chainguard announces the general availability of Custom Assembly and Private APK Repositories for Chainguard Containers. The features let customers customize container images, access Chainguard packages through customer-specific endpoints, and use Chainguard Factory for automated builds and ongoing maintenance. ### Source excerpt Custom Assembly and Private APK Repositories, two new features for Chainguard Containers, are now generally available. ## 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. ## 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 ## 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 ## 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 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 ## Designing build date epoch in Chainguard Images DevFeed: [Designing build date epoch in Chainguard Images]() Original publisher: [Read original article]() Published: 2023-06-08T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [Git](), [configuration](), [APK]() Tags: [apk](), [build-date-epoch](), [chainguard-images](), [container-image](), [cves](), [git](), [images](), [secure-image](), [wolfi]() ### AI overview This article explains how Chainguard Images use deterministic timestamps to remain reproducible without displaying a misleading 1970 creation date. It describes source date epoch, Git commit timestamps, APK package metadata, and the additional build date epoch considerations when images incorporate newer packages to address CVEs. ### Source excerpt Learn how we make Chainguard Images reproducible using build date epoch. ## About the Android Makers app, security and google-services.json DevFeed: [About the Android Makers app, security and google-services.json]() Original publisher: [Read original article]() Author: Martin Bonnin Published: 2022-05-06T13:45:38Z Content type: article Language: en Sources: [Martin Bonnin's blog]() Topics: [Android](), [API keys](), [Security](), [Firebase](), [APK](), [Android Studio](), [Google](), [Google Play]() Tags: [android](), [android-studio](), [api](), [apk](), [firebase](), [google-cloud](), [google-play](), [security]() ### AI overview The article explains why an Android API key in google-services.json is accessible in an app and can be retrieved from a published APK. It discusses the apparent contradiction between that accessibility and warnings about exposing the key in GitHub or Google Play. ### Source excerpt Android Makers is over! With over 650 participants and 50 sessions over 2 days in Paris, it was a lot of fun! It was nice to see everyone in person again and discuss all the Android things (and 🍻 too)! This year, we decided to rewrite the Android a... ## Fixing APK Analyzer terminal errors by selecting a compatible Java version DevFeed: [Fixing APK Analyzer terminal errors by selecting a compatible Java version]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2021-12-12T10:26:38Z Content type: tutorial Language: en Sources: [Dustin Summers]() Topics: [APK](), [Java](), [CI/CD Pipeline](), [Android Studio](), [Command-line interface](), [Google]() Tags: [android-studio](), [android-xmlschema-error-apkanalyzer-troubleshooting](), [apk](), [ci-cd](), [command-line](), [error](), [java](), [jdk]() ### AI overview This tutorial addresses an APK Analyzer error encountered when running the tool from a terminal, including in a CI/CD workflow. It explains that Android Studio's bundled JDK may be incompatible and describes selecting another installed Java version, with guidance for making the change permanent. ### Source excerpt Recently, I was tasked with using Google provided tools to decompile an APK in a CI/CD pipeline. This is great, because Google provides a tool called APK Analyzer, and provide tools both within the IDE itself and options to run it via the Command Line. I can talk more about the actual task later. For now, I want to discuss the issue that I first ran into when attempting to run apkanalyzer from the terminal. ## Reducing Android app size in practice at LinkedIn DevFeed: [Reducing Android app size in practice at LinkedIn]() Original publisher: [Read original article]() Author: Chao Zhang Published: 2021-11-23T16:53:49Z Content type: tutorial Language: en Sources: [Stories by Chao Zhang on Medium]() Topics: [Android](), [App](), [Google Play](), [APK](), [modules](), [Azure]() Tags: [android](), [android-app-bundle](), [android-app-development](), [apk](), [app-size](), [azure](), [google-play](), [jetpack-compose](), [modules](), [optimization](), [sdk]() ### AI overview This article explains how LinkedIn reduced Android app download size in practice. It distinguishes download, install, and storage sizes, then discusses Android App Bundle optimizations and Play Feature Delivery, including their use with the Azure Communication Services SDK for Native Video Meeting. ### Source excerpt Photo: Daniel Romero from Unsplash App size is a key metric impacting user acquisition and retention: If the app is too large to download, users may skip installation or cancel the installation during downloading; if the app takes too much storage space after use, users may choose to uninstall. There are also different measurements of Android app sizes: Download size: The compressed size of the release downloaded by users at install time. Install size: The approximate size of the recent release on the user's device after installation, but before the app is opened for the first time. Space used shown in Storage Settings: Sizes of files under cache directory and other directories under /data/data/com.app.package.name This post mainly focuses on the download size. This is displayed directly in the Google Play console for developers, and also displayed in the about this app section in Play Store. The official documentation on Android Developers already covers many different ways to optimize the app size. However, in this blog post, we would like to emphasize some of the less known yet powerful techniques to reduce app size. These techniques helped LinkedIn to minimize its app size in recent years. Play Feature Deliverya.k.a Dynamic Features, Dynamic Modules, or On-Demand modules Android App Bundle, as a publishing format in Google Play, was recently escalated to the requirement for publishing new applications in August 2021. The app bundle is used to generate multiple optimized APKs. Then the user will only download the specific APK set optimized for their device. The download size savings come from: ABI libraries that do not match the device's processor architecture Resource files that do not match screen density Language resources that do not match the user's device language Application size savings from Android App Bundle (Google I/O 2018) -- https://youtu.be/flU42CTF3MQ Migrating to an Android App Bundle should be a streamlined process. At least this was the case for ## Intercept and edit HTTP traffic from (almost) any Android app DevFeed: [Intercept and edit HTTP traffic from (almost) any Android app]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2021-03-24T17:00:00Z Content type: tutorial Language: en Sources: [HTTP Toolkit]() Topics: [LineageOS](), [HTTP](), [Emulator](), [Android Studio](), [SDK](), [APK](), [debugging](), [dev-tools]() Tags: [android](), [android-studio](), [apk](), [debug](), [emulator](), [how-to](), [http](), [interception](), [sdk]() ### AI overview A step-by-step guide to intercepting and editing HTTP traffic from Android apps using a normal Android emulator, Android Studio, APK installation, and HTTP Toolkit. It explains why HTTPS traffic is difficult to inspect and describes emulator configuration requirements. ### Source excerpt HTTP is used by almost all Android apps to request data, load content, and send changes to backend servers. If you can see and edit these requests & responses then you can understand, debug, and change how any app works, but Android makes this hard to do. By default, almost all apps will use HTTPS but won't trust user-installed certificates. This means that you can't see their traffic with simple proxy tools, and you can't manually trust HTTPS debugging proxies without either editing and rebuilding the entire app, or setting up your own rooted device. Fortunately, there's a quick & easy way around this: you can manually install official APKs into a normal Android emulator, which provides enough access that tools like HTTP Toolkit can capture all traffic for most apps for you totally automatically, and allow you to edit responses in just a couple of clicks. Let's walk through how to do that, step-by-step: Setting up the emulator To get started, you'll need an emulator. It is possible to create and start one using the Android SDK directly (see this article) but it's easiest to just install Android Studio, create an empty project, and use the developer tools provided there (if you're not familiar with these developer tools at all, there's an detailed official guide). To create an interceptable Android emulator, you should create an AVD, that: Can be any device model, though things may be smoother with a popular device like a Pixel 4. Uses an image matching your computer's architecture (ARM64 on M1/M2 Macs, x86_64 on most other computers) since the performance will be far better. Uses a relatively recent stable Android version - Android 7 to 13 should be fine. Uses a 'Google APIs' or 'Android Open Source Project' target image. The 'Google Play' target includes extra restrictions and is not easily interceptable. Once you've created your emulator, start it, and then we need to install the target app. Since we don't have Google Play, you can't do that from the normal app s ## Aircall Journey to Android App Bundle DevFeed: [Aircall Journey to Android App Bundle]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2021-02-18T15:12:51Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [Android](), [APK](), [Gradle](), [Optimization](), [CircleCI](), [feature flags](), [ci]() Tags: [android](), [android-app-bundle](), [androiddev](), [apk](), [ci](), [circleci](), [continuous-integration](), [feature-flags](), [gradle](), [optimization](), [play-store]() ### AI overview Aircall describes migrating its Android app from APK distribution to Android App Bundle to deliver optimized APKs. The article covers APK size reduction, language, density, and ABI splits, Gradle configuration, and planned Play Feature Delivery, with CircleCI and fastlane mentioned for release automation. ### Source excerpt A couple months, we decided to use Android App Bundle (AAB) to distribute Aircall's Android app in Play Store. After analyzing the Aircall Android application package (APK), we found we could deliver optimized APKs to our users -- an overall size reduction of 60%! In this article, we are going to expose our journey to Android App Bundle from our own motivations to the development within the application and the CI with CircleCI and fastlane to release on the Play Store. Why move to App Bundle? Moving to App Bundle had many advantages. The first and main reason was the APK size optimization, to deliver only what the user needs. After looking at our application file, we found that we embedded all native libraries (.so files) of all supported architectures! We could have used the abi split in our main build.gradle but we would have managed 4 APKs with different version code. We also saw we could reduce the resource assets to match the density of the device where the app is installed. Here is what the Aircall universal APK looks like on the inside: APK analysis with Android Studio Optimizing size was not the only advantage we saw. Migrating to AAB will allow us (a little bit) to save the planet! Indeed, with all the MB saved from the downloads and updates, we are using less storage space and consuming fewer energy resources. You can see our MAD Score below. If it hits 1 million downloads we could save 22 TB of data -- really a huge impact. MAD Score data from the Aircall project We were also excited by our future ability to enable Play Feature Delivery to push features to specific users. Since we are already using feature flags inside our applications, this would let us develop features on-the-go for our users. Gradle configuration Moving to AAB was a very smooth process and did not require a lot of configuration code. To replicate this move, on your build.gradle of your application, add the following block to build an AAB file. You will be able to add the language, densit ## Presenting data efficiently in emails DevFeed: [Presenting data efficiently in emails]() Original publisher: [Read original article]() Author: Chao Zhang Published: 2021-01-29T01:25:52Z Content type: tutorial Language: en Sources: [Stories by Chao Zhang on Medium]() Topics: [data](), [Android Gradle Plugin](), [email](), [ci](), [APK](), [dashboards]() Tags: [android](), [android-gradle-plugin](), [apk](), [ci](), [data](), [data-visualization](), [email](), [numbers]() ### AI overview The article presents a simple technique for making email reports more engaging by displaying key metrics with less text and larger numbers. It illustrates the approach with an Android Gradle Plugin upgrade report covering CI build-time reductions and APK size changes, and connects the idea to public COVID-19 dashboards. ### Source excerpt A simple trick to write an email report for your readers Image by Hermann Traub from Pixabay Recently my team wrote an email report to the leadership team on the executive summary of Android Gradle Plugin upgrades. Below is the initial version of the reports in the exec summary section: - We have migrated to Android Gradle Plugin from 4.0 to 4.1. -We have observed a reduction in CI build by 50% at 50th percentile and 32% at 90th percentile. - Our APK size is also reduced by -17% The above looks pretty ordinary. But let's compare it to the following: Less text, larger numbers, much easier for readers to get interested in reading them 🎉 Testimony: I have received more than 5 "wow"s from readers across the company hierarchy for the bottom version. The inspiration is actually from the COVID-19 dashboard of where I live. I came to realize how often it is used in public versus how rare it is used in company emails. ## Debugging Proguard configuration issues DevFeed: [Debugging Proguard configuration issues]() Original publisher: [Read original article]() Published: 2021-01-18T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [debugging](), [Android](), [APK](), [obfuscation](), [builds]() Tags: [android](), [apk](), [article](), [build](), [debugging](), [obfuscation]() ### AI overview A tutorial on diagnosing Android release-build bugs caused by Proguard/R8 configuration. It outlines the roles of obfuscation, code optimization, and resource optimization, and recommends using crash logs and APK contents to investigate issues. ### Source excerpt Introduction It might happen so that there is a bug in your release build while in debug everything works fine. In many cases, it might be an issue with Proguard/R8 configuration. Of course, it is better to test your code thoroughly, properly configure Proguard if you, let's say, load some classes only via reflection and so on. But reality sometimes strikes and bugs might go to production. In this case, the first thing that is needed is to find a bug and fix it. And only then have some retrospective to mitigate such situations in the future. When the bug is in production already every minute counts, therefore it is important to have some plan. Proguard configuration seems complex to someone who didn't work with it, so I recommend to take a look at its main features. Most of the time I'd say that issue is easy can be found and fixed by analyzing crash report logs. But sometimes the log is not that clear. In this article I'd like to introduce the plan to find what part of "Proguard" causing an issue, so you can debug more effectively. [Next page]()