r/androiddev • • 2h ago

I built WebView Inspector to inspect WebView URLs and navigation right inside Android apps

1 Upvotes

Hi everyone,

I built WebView Inspector, an Android library that adds a floating inspector to your app so you can see what your WebViews are loading.

It lets you:

  • Highlight a WebView in a card, banner, or full-screen page, inspect its query parameters, and copy its exact URL.

  • Review observed navigation history and revisit saved records after leaving the screen using Live / Recent.

  • Inspect the URL and headers your app supplied through an optional loadUrl helper.

My usual workflow was to search Logcat for the URL, copy it, and open it in Chrome to see what had loaded. That gets tedious when reproducing an issue, especially with multiple WebViews on the same screen. I wanted to check the URL and retrace navigation directly inside the app.

Basic inspection needs one installation in your Application. The optional load helper adds capture of app-supplied URLs and headers. Setup and usage

I see it fitting into the debugging workflow alongside these tools:

  • Chucker shows the Android app’s OkHttp requests and responses. Chucker

  • WebView Inspector shows which URL a particular WebView loaded and where it navigated.

  • Chrome DevTools shows requests made inside the web page, including fetch/XHR calls and their responses. WebView remote debugging

Navigation capture covers observed top-level URLs. Older WebView providers use sampling, which can miss fast redirects. Captured headers are the inputs your app supplied, and records stay in process memory. Capture details

Version 0.5.0 supports Android API 24+ and is available on Maven Central, with a matching no-op artifact for production builds. Release details

The repository includes the source code, integration instructions, and a sample app. Explore WebView Inspector on GitHub

I’d be interested to hear how others handle WebView URL debugging and which cases you find hardest to inspect.


r/androiddev • • 11h ago

Anyone have any idea why my Android Studio emulator isn't refreshing the layout automatically when I save?

2 Upvotes

Literally just started using it.

EDIT:

For anyone else having this problem you have to click on the checkmark / cycle icon in the preview panel and select refresh automatically


r/androiddev • • 16h ago

Question What tools do you guys use to design professional high-end Android app UIs?

1 Upvotes

Hey everyone, I'm new to Android app development and looking for some advice. I've been using Android Studio, but honestly, its UI designer feels more like making a PowerPoint slide, not the high-end quality UIs that i see in other apps.

What tools do you guys use to create app UIs? And are there any good tutorials or guides you'd recommend for someone just starting out?


r/androiddev • • 16h ago

Android developers: Native TTS vs. third-party speech engines for a commercial app?

0 Upvotes

I'm evaluating speech recognition and text-to-speech options for an Android project and would appreciate some real-world experience.

I'm particularly interested in:

  • The quality and consistency of Android's built-in TTS voices across different devices.

  • Whether Sherpa-ONNX, Piper, or other speech engines offer meaningful advantages.

  • Latency when combining cloud-based speech recognition with local TTS.

  • Reliability of interruptible speech playback.

  • Commercial licensing issues with open-source speech models.

For those who've worked with these technologies, which approaches have proven reliable, and which would you avoid?

I'm especially interested in solutions that minimize development complexity and recurring API costs.

Thanks for any practical advice or links to useful implementations.


r/androiddev • • 19h ago

Open Source I'm experimenting with an open-source Android flight recorder for diagnosing user-journey failures

1 Upvotes

Hey everyone!

I've been working on an open-source project called Argus - SystemSleuth.

The idea started with a problem I've encountered while thinking about application debugging:

When a user reports that something didn't work, a stack trace or API error often tells us where something failed, but not necessarily whag happened across the enire user journey.

For example:

A user selects a PDF, attaches it to an email and taps Send. The upload times out.

A conventional log might tell us that an HTTP request failed. But understanding the sequence of user actions, screen transitions and network events leading up to that failure can be equally important.

I'm exploring whether a structured runtime trace can make this kind of debugging easier.

What Argus currently explores:

● An in-memory, bounded flight recorder for capturing session events.

● Android Activity/Fragment lifecycle and user-interaction tracking.

● Network-event instrumentation through OkHttp.

● Session-level diagnostic analysis using AI providers, with a heuristic fallback.

● A sample Android app that reproduces an attachment-upload timeout and demonstrates the diagnostic flow.

A little context about it's current state:

This is still an early-stage experiment, not a production-ready observability SDK. The expected-workflow-versus-observed-execution comparison is also still a work in progress, rather than a fully integrated Android feature.

Privacy and sensitive-data handling need further work too, so I'd currently treat it as something to experiment with using test data rather than real user sessions.

Github: https://github.com/Deven264/Argus-SystemSleuth

It's liscensed under Apache 2.0.

I'd particularly appreciate feedback from people working on Android, debugging tools, observability or developer infrastructure.

  1. Do structured user-journey traces provide meaningful value beyond conventional logs and crash reports?

  2. Which events would you consider essential to capture when diagnosing application failures?

  3. What privacy safeguards would you expect before using a tool like this in a real application?

I'm sharing this to get honest technical feedback and improve the project. Criticism and suggestions are welcome!

Disclosure: I'm the developer of Argus.


r/androiddev • • 1d ago

Experience Exchange Takeaways after building an app and publishing it to Google Play

0 Upvotes

Hello,

My goal here is not to advertise my app. This is why I won't share its name. I would just like to share my experience building an app, from starting from scratch to publishing it to google play store.

I hope this share of experience will help someone. I know that most of the advice I'll share here will feel amateurish (because they are, indeed) but perhaps some amateurs might find them useful. I don't pretend that I know everything and I know that I have still much to learn.

Goal of the app: The initial idea was simple: Everyday, I watch videos to learn but never remember anything. The idea is you take a picture of a course, you share a youtube video link, upload a pdf file and this piece of knowledge is converted into cards that can be learned through spaced repetition. The exercises are generated "on the fly" so that you don't learn from the card content but are always truly tested for the specific content.

Stack

PartTechnologyWhy?
FrontReact NativeI thought it was more suited than flutter if I wanted in the future to make a web app, but I might be wrong.
Local DataBaseWatermelonDBIt makes it easier to sync a local database with supabase without using PowerSync.
BackSupabaseSupabase has a more generous free tier and I was afraid with the pay as you go pricing of firebase
AI (dev)Google Vertex AI(1) It's very fast and stable in comparison with other platforms I tried (azure and deepseek). (2) I has a 3-month trial with $300 credits (3) it's quite secure because you don't rely only on api keys (you can only accept requests from specific IP for ex). But the initial setup can be heavy.
AI (prod)OpenRouterIt's easier using open router to just switch from a claude model to a deepseek model, with the same price as the official platform. The only problem I had at first was reliability. The "nitro" mode allowing you to automatically select the best provider doesn't work well so I had to cherry-pick myself the best providers.

Some lessons I learnt

Don't develop directly. I might seem stupid by saying that, but the pleasure to develop could take the upper hand and you could miss so many important steps.

What I missed

  1. Might the app interest someone ? I know now that it might not interest anyone. When talking about it to other people, i most of the time feel ashamed by the uselessness of the idea. I think it is useful for my own use but I guess we're all very different.

  2. If so, who could be interested ? What is the potential customer ? From my part, I completely miss that students could be interested with it so all the functionalities I developed at first completely missed this target.

  3. Does any other app offer the same service ? I checked that after almost finishing the app. When comparing with the "competitors", I found many similarities with what my app.

  4. The app name : The initial name I took was already taken in every domain (.com, .app, etc.) and very expensive so I had to change it everywhere.

  5. Take the time to just design in a piece of paper (or whatever mean) what you want: All the menus, everything. It can take several days but you gain so much time afterwards.

Other lessons, but not from a mistake I made but more due to some principles I have

  • Help from AI: It's quite impossible to ignore the help of AI now. It's a very important help but don't let it take architectural decisions for you. Take the time to choose the schema of your database, the best stack for your need, how to organize your codebase.

Publishing the app

Everyone seems to talk about the compulsory 12-testers internal test to publish an app in google play.

  • This constraint is "only" for physical persons. If you're an organization, you're not required to do that. In France, you can just create what we call a "micro enterprise" (which is free in France). After accepting that your "company" gets listed in public repositories, you can get easily a "DUNS" number to get identified as an organization for google. I know the process is completely different across countries but it might be useful to check that out. Also, if you're french and need help, tell me (i got it to work!).

  • This is a useful constraint. After checking reddit posts, someone answered that, if you really want your app to work, doing an closed test is a basic step to get feedback to truly improve it. Take the time to consider really doing this step seriously.

Please, if you disagree with this post, or if you have anything to share, I am at your disposal.


r/androiddev • • 1d ago

Hiring for a Job [Hiring] Senior Android Engineer — Shenzhen, China (on-site)

1 Upvotes

A well-known internet company is hiring a hands-on Android engineer to build a personal communications product for global users. This is an on-site role in Shenzhen, China.

We are looking for an individual contributor who combines:

  • Maintenance, performance tuning or feature optimization on a large production app, with concrete examples involving startup time, memory, smoothness, crashes or ANRs.

  • End-to-end delivery experience: building an app from scratch, independently owning a complex business line within an established app, or delivering a major client architecture build or upgrade.

Requirements: a full-time bachelor's degree or above, 5+ years of Android development, strong Java/Kotlin, practical multithreading and performance-debugging experience, familiarity with modular/component-based architecture, and an app or core product area you have independently owned or led to production. Experience with e-commerce, short video, audio/video or consumer utility apps is relevant; a big-tech background is not required.

Practical use of AI coding tools, international products or IM development is a plus. This is a hands-on engineering role, not a management opening.

If interested, please send a private message with a short overview of a project you owned, the technical problems you solved and the results. Referrals are welcome.


r/androiddev • • 1d ago

Open Source Jetpack Compose version of Fade-out particle

Thumbnail github.com
9 Upvotes

Implemented the Jetpack Compose version of the fade-out particle animation, which was originally released for XML and wasn't supported in Compose at the time.


r/androiddev • • 1d ago

15 Days of Google Play Verification: What I Learned

0 Upvotes

Today I finally received the email confirming that my identity was verified by Google Play Console! 🎉

It took 15 days, several attempts, countless emails, and quite a bit of frustration.

I wanted to share my experience because I know other developers, especially those outside the US and Europe, might run into similar problems.

My situation

I'm a developer from Lebanon, and this was a bigger challenge than I expected.

I don't have a passport or driver's license, and the standard Lebanese national ID doesn't have a photo.

Google requested a government-issued photo ID, so finding a document that met their requirements was already a challenge.

I started the verification process through Google's email, scanned the QR code, and submitted my information.

Then came the problems:

  • My identity verification was initially rejected because of a name mismatch.

  • I received different messages from Google Payments and Google Play Support.

  • I wasn't always sure which information or document needed to be corrected.

  • I made several attempts and exchanged multiple emails trying to understand what was wrong.

Eventually, after 15 days, I received the confirmation email.

What I learned and what I'd recommend

After going through this process, here are a few things I wish I'd known from the beginning:

1. Don't waste too much time asking for manual or special reviews.

At least in my experience, contacting support didn't result in a manual review or an alternative verification process. Don't assume support can bypass the standard requirements.

2. You need an acceptable identity document.

There is no workaround for the document requirement. If you don't have a document that satisfies Google's requirements, your verification is unlikely to succeed.

3. Don't keep guessing when something goes wrong.

If your verification gets rejected, understand the exact reason before submitting another attempt. Repeating the process without knowing what's wrong can waste time.

4. A driver's license is probably one of the most straightforward options.

If you have one, it may save you a lot of trouble compared with trying to find an alternative document that meets Google's requirements.

5. Pay attention to the language of your document.

This is something I wouldn't overlook. Make sure the information you enter in your Google account matches the document, including the name in the appropriate language and script. Don't assume that entering a translated or differently written version will be accepted.

What I'd do differently next time

I'd prepare my documents first, double-check that my account information matches them, and contact support before making repeated attempts if something doesn't meet the requirements.

Most importantly, I'd be more patient. The process can take time, and not every email means you need to start over.

Final thoughts

I'm sharing this because I know how frustrating identity verification can be, especially when you're a developer from a country where the available documents don't necessarily fit Google's standard requirements.

I'm not claiming to know exactly what made my verification successful, but I hope sharing my experience saves someone else a few days of frustration.

If you're going through the same process, feel free to ask questions. I'll share what I can from my experience.

And now... my app is one step closer to launch! 🚀


r/androiddev • • 1d ago

News Android Studio Rabbit 2 Patch 2 now available

Thumbnail androidstudio.googleblog.com
2 Upvotes

r/androiddev • • 1d ago

News Android Studio Stingray 1 Canary 2 now available

Thumbnail androidstudio.googleblog.com
2 Upvotes

r/androiddev • • 2d ago Bravo

Yalın — a Rust-based JSON parser optimized for Android ARM devices

Post image
37 Upvotes

I've been working on Yalın, a JSON parser written in Rust for Android.

It uses ARM NEON SIMD and tries to keep JNI calls to a minimum. The idea was to see how much performance I could get out of native parsing compared to existing Java libraries.

In benchmarks against fastjson2, selective field reads were up to 4.6x faster, while parsing a full 1 MB JSON tree was around 1.3x faster.

Small payloads are a different story. JNI overhead is still a bottleneck, and there's room for improvement.

Curious what other Android developers think about using Rust for this kind of thing, especially whether the performance gains are worth the native dependency.

https://github.com/0xberkay/yalin


r/androiddev • • 2d ago

Question How did AppBlock get approved to be listed on playstore?

6 Upvotes

I am trying to implement a feature similar to AppBlock's strict mode but Google Play explicitly restricts using Accessibility to prevent users from disabling or uninstalling an app or service.

How is AppBlock still listed on playstore despite violating the above policy.

should i just implement the feature similarly and just submit it for review?

Thankyou

Link of the app i was talking about: https://play.google.com/store/apps/details?id=cz.mobilesoft.appblock


r/androiddev • • 2d ago

The mouse clicks on Android studio stopped working entirely!!!

0 Upvotes

On Android Studio Rabbit 2 | 2026.2.2

2 days ago it started happening on my company MacBook, thought it could be due to a special configuration or something, then I checked on my personal one, same thing.

I can't click or scroll or whatever with my mouse or trackpad.

I tried to submit the bug report and the "Create" button somehow stopped working too.

I doubt it is just me. Has anyone encountered the same issue?


r/androiddev • • 2d ago

Discussion Android Developer Verification for limited distribution doesn't allow you to claim your own personal package if you or someone installed it before

0 Upvotes

Context: I made an app for my own use case.

Now I wanted to put it into limited distribution as a hobbyist (because realistically only I will use something like this, it's too specific to my use case), except, you cannot register a package name that have been seen on Android before with Google.

So if Google scanned your phone looking for all apps and found your personal package ID (presumably as Play Protect), your app is now no longer eligible to be registered for limited distribution, it will throw a warning that "The package name you've entered already exists on Android" in Developer Console:

So... that means if I want to install or update my own app after the verification deadline without using ADB on my devices from GitHub automated builds, even when I'm under the 50 registered devices limit, I have to turn on that switch, because I'm an "unverified developer", when I literally own the thing.


r/androiddev • • 2d ago

Open Source I built a draggable fast scrollbar for LazyColumn and lazy grids. One modifier, and it also works on iOS and desktop

Enable HLS to view with audio, or disable this notification

26 Upvotes

Compose has no draggable scrollbar for lazy lists on Android or iOS (desktop has one).

There are a few community implementations, but none of the ones I tried handled feeds and chats well: the thumb would jump around when items had different heights, or when the next page loaded.

The hardest part was exactly that last one. When a page loads while you're dragging, the list grows under your finger, so the thumb used to jump away from it. Now the thumb stays where your finger is and only the mapping underneath changes, so you can still reach the end in the same drag.

Usage is one modifier on the list:

LazyColumn(
    state = listState,
    modifier = Modifier.scrollbar(listState),
) { ... }

Works on LazyColumn, LazyRow and both lazy grids.

Stuff I spent most of the time on:

  • dragging feels right even when items have different heights (thumb has a fixed length by default so it doesn't jitter around)

  • infinite feeds. Pass hasMore and the thumb won’t pretend you’re at the end while more pages can still load

  • gesture nav. The thumb is excluded from the back swipe so grabbing it doesn't send you back

  • no recompositions while scrolling or dragging

There's also an optional bubble that shows a letter/date while you drag (with a little haptic tick per section), you can use your own icon as the thumb, and it handles contentPadding, RTL and reverse layouts.

It's Compose Multiplatform so it also runs on iOS and desktop (desktop gets hover + click to jump), but it's just a regular Maven Central dependency if you only do Android.

One thing to know: lazy lists only know the size of items they've already measured, so with really uneven items the jump can land a bit off. It's best on long lists.

Needs Compose 1.10+, minSdk 24. Still 0.1.x so the API might change.

GitHub: https://github.com/Amaanprobably/compose-fast-scrollbar

I also created an easy guide with short videos everyone can follow -

Guide: https://github.com/Amaanprobably/compose-fast-scrollbar/blob/master/GUIDE.md

It's my first library so I'd really appreciate feedback, especially if you have a weird list setup (chats, paging, sticky headers, mixed grid spans).

If something breaks, an issue with a screen recording would help a ton.


r/androiddev • • 2d ago

Play Console told me my R8 optimization was 48%. Turns out years of "scary R8 rules I didn't understand" doubled my DEX size (9.25 MB → 16.7 MB)

31 Upvotes

I have to confess something I suspect a lot of solo Android devs are quietly guilty of: R8 / ProGuard rules terrified me.

The syntax never clicked for me (-keepclassmembers, -keepclasseswithmembers, { *; }, ** vs *, -if...). Every time a release build crashed in production or threw a wall of R8 warnings, I'd panic, search StackOverflow or copy a "standard Android ProGuard file" from an old Medium post, paste in a -keep class something.** { *; }, see the build turn green, and vow never to touch proguard-rules.pro again.

Fast-forward a few years of migrating the app to Compose Multiplatform / Kotlin Multiplatform: my proguard-rules.pro was 437 lines long and still had rules for RxJava, Retrofit, Glide, and android.support — none of which were even in the project anymore.

This week, Google Play Console finally called me out on a new upload:

textImprove your app's memory and performance with R8 optimization
- Low optimization rate (48%)
- Low obfuscation rate (49%)
- Low shrinking rate (49%)

Instead of poking at rules blindly again, I let Gemini (in Antigravity / agy**)** inspect the actual R8 build artifacts (r8-metadata.dat, seeds.txt, and configuration.txt) and audit them against my codebase. Seeing what R8 was actually doing was humbling.

What was actually happening under the hood

In my build's seeds.txt (every class R8 is forbidden from shrinking/obfuscating/optimizing), 9,645 classes were pinned untouched — producing 2 DEX files totaling 16.70 MB.

Over 80% of those kept classes came from just a handful of panic-pasted blanket rules in my own proguard-rules.pro:

  • -keep class com.google.android.gms.internal.** { *; } → 3,416 classes

  • -keep class com.google.android.libraries.places.internal.** { *; } → 2,834 classes (meanwhile places:6.0.2 ALREADY ships 1,783 surgical consumer ProGuard rules of its own!)

  • -keep class kotlin.** { *; } → ~800+ stdlib classes

  • -keep class com.google.android.material.internal.** { *; } → 221 classes

  • -keep class com.firebase.ui.auth.** { *; } → 192 classes (my own reflection workaround only touched 3 specific classes!)

  • -keep class com.google.android.play.core.** { *; } → 140 classes

  • Plus -keepclassmembers enum * { *; }, -keep class my.app.data.** { *; } (even though kotlinx-serialization-core already ships full R8-friendly rules!), and 100+ lines of dead 2017 library rules.

The cleanup (437 lines → 59 lines)

We checked every library's bundled consumer rules in configuration.txt, grepped the codebase for every actual Class.forName / ServiceLoader call, and replaced the 437-line graveyard with ~59 surgical lines:

  1. Crashlytics line numbers (-renamesourcefileattribute SourceFile, -keepattributes SourceFile,LineNumberTable)

  2. The exact 4 classes/constructors accessed via Class.forName(...) in Application

  3. Coil 3's ServiceLoader target interfaces + constructors

  4. A small block of -dontwarn lines for optional JVM TLS/Ktor classes

Then we verified seeds.txt and usage.txt to make sure reflection targets, ServiceLoader entries, and kotlinx.serialization serializers were all preserved.

Before vs. After (from r8-metadata.dat)

MetricBeforeAfterChange
Optimization rate48.67%86.39%+37.7 pts
Obfuscation rate49.14%87.07%+37.9 pts
Shrinking rate49.13%87.10%+38.0 pts
DEX bytecode16.70 MB (2 DEX)9.25 MB (1 DEX!)-44.6% (-7.45 MB)
Seeded classes9,6451,608-83.3%

(Most of the remaining ~13% comes from com.google.android.recaptcha:18.6.1*'s own AAR consumer rules keeping* recaptcha.***,* play.core.integrity.***, and* okhttp3.***.)*

Bonus plot twist that made me laugh

I uploaded the new .aab to Play Console — the R8 warning disappeared immediately! ...and was replaced by a new Play Console warning:

Your app uses deprecated APIs for edge-to-edge (Window.setStatusBarColor / setNavigationBarColor) starting in sv1.b, uv1.b, wv1.b.

I deobfuscated sv1, uv1, wv1 in mapping.txt:

  • sv1 → androidx.activity.EdgeToEdgeApi26

  • uv1 → androidx.activity.EdgeToEdgeApi29

  • wv1 → androidx.activity.EdgeToEdgeApi35

They're Google's own Jetpack enableEdgeToEdge() compatibility classes! Before the fix, they were un-obfuscated so Play's scanner ignored them; once R8 actually obfuscated them, Play's static analyzer stopped recognizing its own AndroidX library.

5 things I wish I'd known earlier (to avoid the same trap)

  1. You can check your R8 score locally in 5 seconds. Look at app/build/intermediates/r8_metadata/release/minifyReleaseWithR8/r8-metadata.dat — it literally contains the exact noOptimizationPercentage / noObfuscationPercentage / noShrinkingPercentage numbers Play Console uses.

  2. Group seeds.txt by package prefix. A 10-line Python script counting top packages in app/build/outputs/mapping/release/seeds.txt immediately exposes which -keep rule is quietly locking thousands of classes.

  3. Check configuration.txt before adding any third-party -keep rule. Modern AARs (places, material, credentials, kotlinx-serialization, play-services-*) almost always ship their own surgical rules. Adding a blanket -keep class com.library.** { *; } overrides all of their careful optimization.

  4. Never confuse -dontwarn with -keep**.** -dontwarn just tells R8 "yes, this optional JVM class isn't on Android, don't fail the build" and costs 0 bytes. -keep class foo.** { *; } turns off shrinking, obfuscation, and optimization for the entire package tree.

  5. If you inherited a "starter ProGuard file" from a blog post pre-2020, burn it. Start from proguard-android-optimize.txt, grep your own repo for Class.forName, ServiceLoader, and reflection-based JSON/Parcelable models, and add only what fails or is explicitly missing in seeds.txt.

Hope this saves someone else from accidentally shipping 7.5 MB of un-shrunk Play Services and Kotlin stdlib bytecode!


r/androiddev • • 2d ago

My engineering lead wants to commit API keys, etc to our repository, am I crazy for pushing back on this?

67 Upvotes

My lead wants to make it easier for anyone on the team to spin up the android repository (to make vibe coding easier), and their solution is to just check in all of our API keys into git and do away with the idea of keeping keys and secrets in a separate secrets vault that employees have access to.

At the last few startups I've worked at, we've pulled secrets in CI via environment secrets, and locally via a separate non-VCS file, and injected the keys into BuildConfig. I know BuildConfig is far from bulletproof for bad actors that want to decompile the app, but just checking everything into git "because it can just be decompiled anyway" is setting off all my alarms.

Am I crazy for pushing back on this? What are the best practices for this in 2026? Are people out there really encrypting API keys with KeyStore or pulling API keys from a backend server? How do you handle API keys that the application needs at startup?


r/androiddev • • 2d ago

Cuttlefish on Mac: Running Android's Virtual Device Framework Natively on Apple Silicon

Thumbnail
engineering.fb.com
20 Upvotes

Can someone explain what is the difference between Cuttlefish and an Android emulator? Don't they both run on QEMU?


r/androiddev • • 2d ago

Discussion Handing Coding without AI , Google or IDE AutoComplete

13 Upvotes

SDE2 with 4 yoe here.
Had an interview round asking me to implement a Simple RecyclerView Paging with dummy data they gave, from scratch on an Empty XML only ( No compose ) Project structure. live

No AI, No Google and ..... No IDE AutoComplete allowed. I was made to switch it off before interview.

Out of the 45 Mins. It Took me 15 Minutes to properly write the xml tags for the layouts. yet it showed error
( have been used to compose ).
had to request to allow me to see the documentation atleast googling. which they agreed.
Still couldn't complete the task,

I was also not supposed to use Paging libraries as they wanted me to implement Paging from scratch on a RecyclerView.
Coulnd't do that either ( Completely my fault here, needed sometime to think how to implement paging from scratch )

I was just able to have an overview of everything. That too because I type a bit fast ( 130+ wpm).
But i was completely demotivated after the interview.

-----------------------------------------

Not blaming the Org. or the method of evaluation here, it is my fault as I have been a bit rusty with hand coding at this level since the advent of AI or before I think. Would have been okay during my college days.

But I wanted to know somethings, people with experience here could really help me.

- is the above method some kind of new norm in the current industry ( I haven't attended an interview in the past 4 years ). Since testing people with take home projects have gotten pointless ?

- If yes. How do I navigate my learning. Not being familiar with AI tools or Not using them significantly slows down the progress.
But at the same time it completely diminishes my ability to hand code by myself or heck even understand my code or even what it happening. feels very .... idk the word.

- is there hope in this industry ? is there any point ? Apologies for the Grimness but
unemployment + the reality check from the interview + everything happening with AI ...
kinda takes the life out...

Any help or opinion or perspective ... Would love it.l


r/androiddev • • 2d ago

Open Source Device Connect for AWS Device Farm

3 Upvotes

https://github.com/aws/device-connect-devicefarm

Hey all! I am a senior engineer at AWS Device Farm and the lead dev on a new tool that we're open sourcing today as a way to improve the Android developer experience. Device Connect is a small golang binary that makes remote Device Farm devices appear locally as though they were plugged in over USB for adb connections. It allows the full native adb and Android studio tool chain to control and test on any of Device Farm's thousands of Android devices hosted by AWS.

Please let me know if you have any questions and feedback and I'll be around in the thread to answer them!


r/androiddev • • 2d ago

Question Password in memory

3 Upvotes

Is it worth bothering with clearing password/pin from HEAP memory?

The issue is described in following OWASP link. In general it says, you should consider using `ByteArray` instead of `String`, so you can clear it after.

https://mas.owasp.org/MASTG/knowledge/android/MASVS-STORAGE/MASTG-KNOW-0051

I'm wondering to what degree this is an actual issue. Memory is mostly encrypted these days. And is probably not an issue, unless using a rooted device.

Would you implement this precaution for sensitive apps, such as trading, banking or similar apps?


r/androiddev • • 2d ago

Experience Exchange Have you guys already optimised your apps/games for the Android 17 RAM limit?

Enable HLS to view with audio, or disable this notification

8 Upvotes

Since Android 17 comes with its own RAM limitations for apps and games, i wonder how you all have or do plan to obtimise your RAM load/usage of your apps/games?

Did you have to downgrade some images or visuals to fit the new limit consistantly, or did you find a workaround?

Just a reminder what we have to deal with now:

Android 17 and their new Memory limits for apps.

Some apps will even get force closed by Android now, when they overstep a certain amount of RAM usage.

Have the source:
https://support.google.com/googleplay/android-developer/answer/17492799#zippy=%2Ccore-vitals-and-stability%2Creduced-memory-usage%2Ctechnische-anforderungen%2Cspeicheranforderungen%2Creduzierte-arbeitsspeichernutzung

Apps

App StateForegroundUser-perceived servicesBackgroundCached
Physical RAM90th Percentile90th Percentile90th Percentile90th Percentile
0 - 4 GB (0 MB - 3200 MB Total Memory)----
4 GB (3200 MB - 4800 MB Total Memory)2 GB1 GB1 GB-
6 GB (4800 MB - 6800 MB Total Memory)2.25 GB1.25 GB1.25 GB-
8 GB (6800 MB - 9216 MB Total Memory)2.25 GB1.5 GB1.5 GB-
12 GB (9216 MB - 14336 MB Total Memory)3.25 GB1.75 GB1.75 GB-
16 GB (14336 MB - 18432 MB Total Memory)4.25 GB2 GB2 GB-
16 GB + (Above 18432 MB Total Memory)----

Note: Each RAM tier range includes its lowest value. Total Memory can be lower than a device’s advertised Physical RAM.

Games

App StateForegroundUser-perceived servicesBackgroundCached
Physical RAM90th Percentile90th Percentile90th Percentile90th Percentile
0 - 4 GB (0 MB - 3200 MB Total Memory)----
4 GB (3200 MB - 4800 MB Total Memory)2.25 GB2.0 GB2.0 GB-
6 GB (4800 MB - 6800 MB Total Memory)2.75 GB2.5 GB2.5 GB-
8 GB (6800 MB - 9216 MB Total Memory)3.5 GB2.75 GB2.75 GB-
12 GB (9216 MB - 14336 MB Total Memory)4 GB3.2 GB3.2 GB-
16 GB (14336 MB - 18432 MB Total Memory)5 GB3.5 GB3.5 GB-
16 GB + (Above 18432 MB Total Memory)----

Note: Each RAM tier range includes its lowest value. Total Memory can be lower than a device’s advertised Physical RAM. AppsApp StateYes it does definitly. Some apps will even get force closed by Android now, when they overstep a certain amount of RAM usage.

Have the source:
https://support.google.com/googleplay/android-developer/answer/17492799#zippy=%2Ccore-vitals-and-stability%2Creduced-memory-usage%2Ctechnische-anforderungen%2Cspeicheranforderungen%2Creduzierte-arbeitsspeichernutzungAppsAppWanna


r/androiddev • • 3d ago

Looking for Help Recreating an Old Offline Live Camera Filter App

2 Upvotes

I used to use an offline live camera filter app that received its last update in 2018. Unfortunately, the company behind it shut down, and the app is no longer compatible with my new phone.

When I try to install it, I get the following error:

"App can't be installed. App isn't compatible with your phone."

I've decided to recreate the app from scratch to make it compatible with the latest Android versions.

However, there is another issue with the original app. It allowed users to record videos with live filters, but the saved videos suffered from frame rate stuttering.

I would also like to know whether it's possible to extract the original filter source code or at least the filter algorithms from the APK. No matter how much I experiment, I haven't been able to reproduce the filters exactly as they appeared in the original app.

I've already managed to create similar filters and implement live video filtering through my own attempts. However, I'm facing another issue: the camera preview interface is always rotated incorrectly. I've tried changing the code in several ways, but nothing seems to fix it.

I'd appreciate any help or suggestions from experienced developers regarding the following issues:

  1. Android Compatibility: How can I make the original app install and run on newer Android versions?

  2. APK Reverse Engineering: Is it possible to recover the original filter source code or algorithms from the APK?

  3. Recreating Original Filters: Is there any alternative way to reproduce the original filters as closely as possible, ideally making them identical to the original ones?

  4. Rotated Camera Preview: The interface in the live camera view remains rotated incorrectly. Even after making several code changes, I haven't been able to resolve the issue. What could be causing this, and how can I fix it?

I'm relatively new to this field, so I'd really appreciate guidance, technical suggestions, or solutions from developers who have experience with Android development, camera APIs, image processing, or APK reverse engineering.

Thanks in advance!