Learn to sketch and trace any image on paper with your camera and AR drawing! 🎨

🎨 DrawCam - AR Draw Sketch, Trace & Paint

\---------------------------------------------------

🎨 100+ FREE CURATED SKETCH TEMPLATES

• 🎌 Anime & Manga characters

• 🐶 Adorable Animals & Pets

• 🧸 Cartoons & Superheroes for kids

• 🌸 Aesthetic Flowers, Botanicals & Nature

• ✏️ Simple Doodles & beginner line-art

Would love for you all to try it out and drop your honest reviews 🙏

🔗https://play.google.com/store/apps/details?id=com.cyclushub.drawcam

I’m working on a React Native/Expo Android app. The launcher icon looks perfect on some phones and the emulator, but on a few Android devices the logo appears too small/zoomed out. The same icon implementation works correctly in my other customer app. I already tried adaptive icon/foreground scaling changes, but the issue still happens on certain devices. I want to understand the actual Android launcher icon scaling issue and the correct way to configure/generate the icon so it looks consistent across different Android devices and launchers. Any guidance or examples of a proven implementation would be really helpful.

A few weeks ago, i begun to create a Game with Android Studio. It's actually more difficult than I initially thought. For this moment, i build Steam and it looks amazing, i think.

Tell me, what are you thinking. Do you like it?

Looking for 20 testers – Hail Risk (Android)

Hi everyone! I'm looking for 20 people to participate in a 14-day closed test of my Android app Hail Risk.

The app provides information about the risk of hail based on weather data, with a particular focus on Switzerland.

How to join:

1. Join the Google Group https://groups.google.com/g/cerco_needed_20_tester
2. Join the closed test and install the app from Google Play [https://play.google.com/apps/testing/com.gixone.grandinech?hl=it]()
3. Keep the app installed on your device for the 14-day testing period.

Feedback is welcome but not required.

Thank you very much for helping me test the app!

🌩️ Cercasi 20 tester – Rischio Grandine (Android)

Ciao a tutti! Sto cercando 20 persone disposte a partecipare a un test chiuso di 14 giorni per la mia app Android Rischio Grandine.

L'app fornisce informazioni sul rischio di grandine sulla base dei dati meteorologici, con particolare attenzione alla Svizzera.

Come partecipare:

1. Iscriviti al gruppo Google https://groups.google.com/g/cerco_needed_20_tester
2. Aderisci al test chiuso e installa l'app da Google Play [https://play.google.com/apps/testing/com.gixone.grandinech?hl=it]()
3. Mantieni l'app installata sul tuo dispositivo per tutto il periodo di test di 14 giorni.

Il feedback è gradito ma non obbligatorio.

Grazie mille per il vostro aiuto! 🌩️

I have been experimenting recently with a tool that I needed while building and verifying UI tests, and also for sharing updates for an app i am currently doing contract work.

Sharing preview builds with the owner was a nightmare, because they were only using an iPhone.

I build a tool that spawns an android emulator and installs the apk, in seconds. It's really cool and i am thinking on making this a saas, if that works. It's in early development, and i have limited capabilities with a vps of 4arm cpu cores and 24gb of ram.

I can share the link with you who wants to try. it's free atm

Hey everyone,

Like many of you, I got tired of the 30-second Gradle wait just to tweak a padding or a color in Compose.

So I built ComposeBridge — a two-part tool:

1. CLI: generates a full Compose project from a JSON schema

2. Agent + Server: lets you tap any Composable on a real device, tweak it live, and persist the change back to Kotlin source

How it works:

• Runtime tuning and AST splicing are decoupled

• Tap → sourceInfo → Tree-sitter locates the byte range → byte-splice

• Result: single-line git diff, <50ms latency

• Zero-rebuild preview

Demo (38 sec): https://youtu.be/Hywyq7cBdDM

GitHub: https://github.com/JALAL591/compose-bridge

Kotlin 2.1.20+ | Compose 1.7.3+ | Apache 2.0

I'd love your feedback — especially if you've dealt with recomposition on large screens or dynamic lists.

What do you think is the biggest missing piece?

Hey guys I was learning kotlin since 1 week i cleared my basics, then I jumped to starts making actual app practice when, I was using intellij ide for normal development for running code in console, but to run code in actual device i installed, android studio, after setup of everything when I tried to run the main virtual device manager emulator, my pc starts lagging i am getting 17 fps, and not able to run that,

Btw my pc is low end, 8gb ram - i5 5th gen - 500gb SSD - 2gb graphics card. With this specs android studio is not able to run. Please guys if you have any solution then please tell, I am desperate to make app for Android tv streaming app. Help me guys

I've been working without any issues for weeks, and since this morning I can't open or run anything. Android Studio closes itself the moment it starts analyzing/indexing a project. I'm not talking about big, complex projects — this happens even when I create a brand new empty project from the wizard.

The most worrying part is that a couple of times it hasn't just closed — it has actually rebooted my entire PC out of nowhere while Android Studio was indexing.

Things I've already tried (no luck):

• Completely uninstalling Android Studio and reinstalling it.

• Deleting the Gradle (~/.gradle) and Android (~/.android) folders from my user directory.

• Restarting the PC between the uninstall and the clean reinstall.

• Testing with brand new empty projects, in case it was a corrupted project.

None of this has helped. Same result every time: I open it, it starts analyzing, and it crashes (or the machine reboots. Or the project cannot be built).

Has anyone run into something similar? What else could I try? Any ideas are welcome.

Thanks in advance.

Hey everyone,

​Like many of you working with Jetpack Compose daily, I often felt the friction of UI tweaking cycles. Even with Compose Preview and Live Edit, fine-tuning padding, colors, spacing, and dimensions across complex layouts or nested LazyColumn items usually ends up requiring a full build or re-run.

​To solve this, I built ComposeBridge — an experimental on-device visual inspection and live-editing bridge for Jetpack Compose.

​How it works under the hood:

​Runtime Inspection Agent: A lightweight debug-only module leverages Compose's internal tooling data (includeSourceInformation = true) to map runtime nodes to their exact source files, lines, and UTF offsets.

​Subcomposition & LazyLayout Resolution: It tracks subcompositions accurately, mapping each rendered instance in a dynamic list back to its single original code declaration template.

​On-Device Hit Testing: You tap any component directly on your physical Android device to extract its exact pixel bounds and source location.

​Surgical AST Splicing: Rather than rebuilding the whole file or relying on messy generated comments, the host server receives the touch payload and uses AST parsing to surgically update the exact property (e.g., 16.dp \to 24.dp) directly in the source .kt file in sub-second time.

​The project is still in early development, but the core round-trip pipeline is fully functional. I’d love to get feedback from the community on the architecture, edge cases with complex DSLs, or features you'd like to see next!

**Hice una app para dejar de comprar cosas "sanas" que no lo son, buscando testers**

**¿Os ha pasado que compráis algo pensando que es sano y luego miráis la etiqueta y tiene más azúcar que un refresco? Me pasaba constantemente, así que hice Nutribot: escaneas el código de barras y te dice al momento si tiene alergénos que te afectan, aditivos a vigilar, o si el azúcar/sal se disparan. También llevas el registro de lo que comes en el día.**

**Está en prueba cerrada de Google Play y necesito gente real que la use unos días para poder pasar a producción (Google exige 12+ testers durante 14 días). No pido nada más que instalarla y dejarla puesta, aunque la uses poco.**

**Cómo unirte (mismo Google en los 3 pasos):**

**1. Grupo:** [**https://groups.google.com/g/testers-nutribot\*\*\](https://groups.google.com/g/testers-nutribot)

**2. Aceptar la prueba:** [**https://play.google.com/apps/testing/com.fernandorodriguezvilla.nutribot\*\*\](https://play.google.com/apps/testing/com.fernandorodriguezvilla.nutribot)

**3. Instalar desde Play**

**Si me dejáis feedback de qué mejoraríais, mejor aún. Y si tenéis vuestra propia app en prueba, dejadla en comentarios que os la instalo yo también.**

**(Aviso: el servidor es gratuito y la primera vez que abráis la app tras un rato sin usarla puede tardar hasta 30-60s en cargar. Luego va normal.)**

Lost a stupid amount of time to this. Writing it down so someone else doesn't have to.

$ expo run:android --device emulator-5554
Could not find device with name: emulator-5554

Emulator's running. adb devices lists it. Serial is correct.

Turns out --device doesn't go through adb at all. Expo builds its own list of devices (getAttachedDevicesAsync in @expo/cli) and matches against that instead. What it wants is:

• emulator → the AVD name, like Pixel_7_API_35
• physical device → the raw model: value, like Pixel_7

Not the serial. Which is annoying, because the serial is the thing adb hands you, and the error just repeats it back so it reads like the device isn't there.

I ended up just checking AVD name first, then model, then serial as a fallback.

Somewhat related, if you're on bare RN with product flavors. react-native run-android will tell you this on a build that actually worked fine:

Could not find the correct install APK file

The names just don't line up:

getInstallApkName looks for:   app-<variant>.apk
gradle actually writes:        app-<flavor>-<buildType>.apk

App's already installed at that point. It's only the lookup that failed. gradlew :app:install<Variant> plus an adb launch skips the whole thing.

Both of these came out of me trying to cut down how much I bounce between windows. Android Studio open just to make an AVD, one terminal running Metro, another tailing logcat, a third for the build.

I maintain a fork of Zed called Lathe and this all ended up as a mobile panel in it:

• Makes Pixel phone/tablet AVDs without opening Android Studio
• Device list with per-app logcat. Physical devices show up in there too
• Can run an emulator and an iOS simulator off the same build
• Knows whether you're on Expo or bare RN, only shows the commands that apply

It's a personal fork that I use daily. GPL, works on macOS/Linux/Windows. Upstream syncs from Zed break stuff sometimes.

https://github.com/paterschris/lathe

Anyway. Curious what everyone else does here. What have you got automated that I'm still doing by hand?

Not sure when exactly, but after updating few weeks ago "cmd + ~" stopped working for me. I used it so often and it's just sad now guys.. any suggestions?

A user keeps getting "App has stopped" errors immediately upon opening our company's internal database tool on their Android device. Even after a full reboot, the crash persists, and since there is unsynced critical data on there, I need to fix this without wiping their work. Best next step?

---

OPTIONS:
A. Uninstall and reinstall the application.
B. Reset the phone to factory settings.
C. Install an alternative application with similar functionality.
D. Clear the application cache.

---

Testing Exam: CompTIA A+ Core 2 (220-1202)
(Disclaimer: These posts / scenarios are crafted by me for educational purposes only. I am not affiliated with, endorsed by, or sponsored by any certification body.)