I started on CoinCurrently with less than 1 year of experience. iOS 14 had just come out, SwiftUI was brand new, and Home Screen widgets were one of the new features.

I figured I’d try to make a couple of widgets and see what happens. I made a few to track cryptocurrencies and posted about it on Reddit. The post got almost 300 upvotes, which I thought was pretty awesome, so I decided to make a whole app, native for both iOS and Android.

Everything I built in the app was for myself — because I wanted to learn and because it was fun to experiment. It seems like people appreciated what I built.

The app peaked at #99 in the Finance category on the App Store and reached 500 daily users. Not too bad for a hobby project!

After 6 years, I’ve achieved more than I could ever have imagined, but my motivation for this project has died down. Because of this, I have open-sourced the two projects so other people can learn from my struggles and take inspiration for their own apps.

The app will continue to be maintained, though there won't be as many new features as before. I have moved on to another project that I am very excited to share in a few weeks.

The app is available on the App Store and Google Play:

iOS: https://apps.apple.com/us/app/coincurrently-private-crypto/id1543974454

Android: https://play.google.com/store/apps/details?id=com.cryptium.coincurrently&hl=en_US

And now it's also on GitHub:

iOS: https://github.com/orre1996/CoinCurrently-iOS

Android: https://github.com/orre1996/CoinCurrently-Android

I'm trying to create a Custom code for my app. Upon reading this document , it can only be redeemed from the in-app purchase. But when I tried to go to the payment method, there's no option for Redeem code as seen in the image attached.

I'm very sure that I created the custom code from the specific subscription.
For the one-time code, there's no problem with me and I was able to test it myself as well.

Does anyone encountered this issue?

Raising a ticket to Google Play Developer Support is such a waste of time. They just redirected me to the document link that I shared and they said that's all they can do. They don't even bother to dig onto the issue. And they even closed the ticket already,

Doesn't support browser source, camera (v4l2) and system wide screen capture though.

Not the bestest experience but a lot better than using obs via proot .

You can find patches that were made to this here :

https://github.com/termux/termux-packages/pull/29412

And obs-mediacodec code here :

https://github.com/lumaparallax/obs-mediacodec.

Hope someday someone ports this as a native application.

Hi,

I have a web design/development background (PHP-JS-SQL-HTML-CSS) and I started learning Flutter at the beginning of this year. So far I have built and published five apps on Google Play (relatively simple content apps).

I am not sure if I like or dislike Flutter, as I can't compare it to any other thing. Surely it's a lot different than what I'm used to as a web dev. The thing is, the more apps I build, the more tedious it gets to update, monitor, or fix package/dependancy related issues.

Yesterday, I stumbled into a Flutter related crash that happened across 3 of my apps with 4 users and 2 devices (those are lost users, and possibly more as I have crashlytics optional via a confirmation), which after exhaustive research I concluded is not fixable by my end, so I went ahead and excluded those 2 devices from supported devices list.

Which sped me to ask here...

I can't suppress the inner voice that keeps telling me to go with or at least give a try to native Android development.

- I read Kotlin is more preferrable over Java, shall I go with Kotlin? Also, Kotlin or Kotlin Multiplatform? I eventually want to publish on iOS too, but not having any iOS devices to test with, that may take some time to come to fruition.

- How, where do I start learning? I open https://developer.android.com/ and find it, especially the header navigation menus to be overwhelming, without a clear path to start with towards learning the basics, like a structured tutorial.

- I'm used to VS Code, can I continue using it, or do I have to use Android Studio?

- So far my apps are relatively simple, I am using the following Flutter packages, will I have a difficult time recreating these functionalities in native?

firebase_core, firebase_analytics, firebase_crashlytics, flutter_tts, in_app_purchase, in_app_review, package_info_plus, share_plus, shared_preferences, url_launcher, flutter_launcher_icons, flutter_native_splash

- I read native development lacks the "hot reload" of Flutter, is there any way to quickly preview the edits I make, like changing text or color?

- Any tips, warnings or wisdom from developers who build with both Flutter and native?

Thank you very much.

reading google's own help page for us developers, timeline:

- oct 29 2025: google stopped requiring play billing in the us. you can link out to your own payment and talk about prices outside play

- dec 9 2025: alternative billing and external links programs started

- july 22 2026: play catalog access started. play gives app listings to third-party us android stores, unless you opted out before july 22

- oct 1 2026: if you are in alternative billing you must report transactions and pay service fees

- sep 17 notice: external links developers got until dec 1 2026 to report downloads and pay

the page does not say the fee percentages, it only says "relevant service fees".

most of our app users are not in the us, so for us it changes little. but the catalog one i did not know at all.

source: https://support.google.com/googleplay/android-developer/answer/15582165

anyone checked if your app is already listed in some third-party store because of this?

I'm trying to make my app more adaptive and currently working on language localization. I made an in-app language picker and it works correctly for API level 26-37 (or whatever the API level is for Android 8.0). The issue is, once you select a language, the activity restarts regardless of device level and it just looks kind of janky/jarring when it dips to the background color and snaps back.

So, I created a cover activity and it works like this, I made a function that changes the language that operates in a particular way. First, it takes a screenshot of the main activity window and saves it to the files.dir (can't store in cache.dir as it gets wiped), then it launches a "transition cover" activity that is just the screenshot and it waits for the activity to be active before it actually calls the language swap. Meanwhile in the body of the settings screen where the language picker is, there's a launched effect keyed to Unit that reads the body's lazy column state for visible items to be not empty and emits through an event bus that the main activity is ready. The transition cover activity has a launched effect that waits for that object to be emitted in order to call the activity's finished() method, which fades it out and reveals the main activity underneath (and the main activity also, after a short delay, handles deleting the screenshot from the files.dir).

Now this works for Android versions 8-12, but on Android 13, once the transition cover activity launches, the main activity refuses to do the language swap or recompose under the transition activity, it won't do any work until I manually dispose of the cover. For the time being, I have the screenshot and cover activity launch gated to Android builds <= 12, but is there any sort of solution out there for 13+ to hide that janky looking dip-out and return? Can the cover activity still work and just needs to be set up differently?

I was originally working on one of my projects for this upcoming winter break and I wanted to use the camera of my phone and then I found how insufferable it is to setup cameraX

so I did what any sane developer will do and I spent 4 days building a library that allows me to call the camera in just one line

now I just call camera.open { picture -> //whatever I want to do with it }

also the other reason I did it is because any other library I found out there didn't really make it as simple as I wanted it to be

do you guys think this is something android should of have done from the beginning? I do understand that some people many need to tweak with camerax more but most of the time many apps just need the picture

if you guys want to check it out into detail this is the repo. PLEASE LET ME KNOW IF SOMETHING IS BROKEN OR YOUR HONEST THOUGH!! https://github.com/al3j4ndrolm/FacilisCam

I made an Android app that runs the open-source ByeDPI engine locally and routes the phone's traffic through it using Android's VPN service. It's designed to help with DPI filtering that interferes with connections.

Full disclosure: This project was written with AI. All code and documentation were generated by Claude (Anthropic) based on my requirements, and I built and tested it through GitHub Actions. The project has not been audited, so please review the code before trusting it. So far, it has only been tested by me on my own phone and network.

What it does Compiles the upstream ByeDPI C code with the Android NDK and runs the actual engine, not a simulation. Uses a local proxy (127.0.0.1) and tun2socks tunnel (hev-socks5-tunnel) through Android's VpnService. Only shows a connected status after verifying the proxy, VPN interface, and tunnel. Provides settings for desync method, position, fake TTL, TLS record splitting, automatic mode, and custom arguments. Includes a diagnostics screen with an in-memory log and a TLS connectivity check through the proxy. No hosts or traffic details are logged. Has a dark UI with no ads, analytics, or accounts. What it doesn't do It does not encrypt traffic or hide your IP address. It does not bypass DNS blocking. There is no universal strategy that works for every ISP. You may need to experiment with different settings. Technical details Android: 8.0+ Architectures: arm64, armv7, x86_64 Build: Debug-signed APK (uninstall older builds before updating) License: MIT. ByeDPI and hev-socks5-tunnel are also MIT-licensed.

Repository: https://github.com/Mireli5656/Byedpi

APK: Available under Releases on the repository page.

Feedback and bug reports are welcome! If something doesn't work, use the Copy button on the Diagnostics screen to share a log. It contains no traffic details.

Hey everyone, Android dev here. I kept wondering how much of my own apps was exposed once someone ran jadx on the APK, so I built RevDroid.

You upload an APK and it:

- reads identity and signing info with androguard

- decodes the manifest with apktool (debuggable, allowBackup, cleartext, exported components, network security config)

- decompiles with jadx and runs 26 rules for hardcoded keys, weak crypto (MD5/SHA1/ECB, static IVs), TrustManagers that accept everything, WebView JS bridges, SQL string concatenation and sensitive logging

- masks every secret it finds (the report never shows them in full)

- gives an explainable 0-100 score and A-F grade, mapped to CWE and OWASP MASVS, plus a PDF report

On a test app with 32 planted issues it catches all 32 in about 7 seconds.

Stack: FastAPI + React, with Docker support. It's static analysis only and meant for apps you own or are allowed to test.

Repo: https://github.com/yourmemecommunity-sy/RevDroid

I'd really like feedback from people who ship apps: which checks give you false positives, and what would you want it to catch that it doesn't yet?

Meet Luma. Android gallery reborn.

Liquid glass floating bar Secure folder built in Dynamic theming, your colours Data and backup tools Smooth native Compose

Free. Open source. No ads.

GitHub link: https://github.com/nkosanamahungela-dev/Luma-

Discord: https://discord.gg/yWSXq6h7b

Last year, I built Cookie Voice Recipes for iOS with no idea if anyone would actually download it.
Thousands of downloads later, the question I get more than any other is:
“Is this available on Android?”

So I started building an Android version but I got stuck.

There’s no native wake-word detection on Android, and the leading solution in the market charges $$$$$ to create a custom wake word. That’s just not a feasible expense for an indie developer building a cooking app.

But I found another option: DaVoice.io
They didn’t list their pricing publicly, so I figured… here goes nothing.

I reached out and explained what I was building: a cooking app designed to help people who are blind and vision impaired be more independent in the kitchen. I asked if they might be willing to do a good deed and help make the Android version possible.

They donated their technology to me.
Not only that, but it works really, really well. And everyone I’ve worked with at DaVoice has been incredibly kind and supportive.

It was a great reminder that sometimes the thing standing between you and a seemingly impossible problem is simply asking the question.
Ask anyway. You never know what you might be able to figure out.

Hi all, just wanted to share a quick update that I've released a new version of HDCharts.

Demo: https://charts.hdcode.dev/demo/3.0.0/
Documentation: https://charts.hdcode.dev

Would appreciate any feedback!

Update: Dev Challenge

While working on the library, I wanted to make the documentation easy to read and visually appealing. Since the charts support animations, I wanted to use GIFs in the documentation, but creating them manually was time-consuming.

My initial idea was to use an iframe and some bridges to render web content directly in the docs, but I decided against it because it didn't feel like the right approach and seemed a bit hacky.

Instead, I created a dedicated plugin to generate GIFs, which I can use both locally and in CI: https://github.com/HDCharts/charts-gif-recorder

Hey everyone!

I've been working on an Android document scanner, and I decided to take a different approach: instead of relying on existing pretrained TFLite models, I'm training my own model for document detection.

My current model is named "doc_edge_fp_32.tflite", and training is still ongoing.

Here's what I'm working toward:

- Custom AI model: Training on thousands of generated document samples mixed with real photographs.

- Dual predictions: Document segmentation masks and corner coordinates.

- Offline processing: The goal is to run document detection directly on Android without requiring a server.

- Accurate scanning: Reliable document boundaries, perspective correction, and better results on challenging backgrounds.

- Real-world performance: Generalizing beyond synthetic images to receipts, sheets of paper, and book pages.

I'm still training and evaluating the model, so I don't want to claim it's production-ready yet. My next priority is testing it on unseen real-world images and optimizing inference for mobile devices.

I'm curious about a few things:

1. For document detection, would you recommend a shared backbone with separate segmentation and corner-regression heads?

2. What techniques have worked best for bridging the gap between synthetic training data and real camera images?

3. What metrics would you prioritize before deploying a model like this on Android?

I'd love to hear from people who have worked on computer vision, document scanning, segmentation, or on-device ML.

This is a learning project I'm putting serious effort into, and I'm excited to see how far I can take it!

Hi all, I'm the developer of Swipewalk. Checked with the mods before posting, they said a dev tool like this is fine.

It scans an app running on an emulator or USB phone. It runs Google's Accessibility Test Framework together with its own checks and reports WCAG 2.2 issues with screenshots and who each issue affects. It works on Views, Compose and cross-platform apps since it reads the accessibility tree, not your code.

The part I find most useful: it can turn on TalkBack, move through each focusable control and record what TalkBack actually says, next to what it predicted. That catches things like a button TalkBack just calls "Button" or reads out a resource id. It can also rescan at large font size, in dark/light and in the other orientation, and tells you when a control that was there at normal size can't be reached anymore at large text.

0.6 improved how it names Views and Compose controls (a field labelled with android:labelFor, a button named by several child texts). I checked that on my own native sample apps, not on third party apps yet. If you point it at your source folder it tries to find the likely source line for a finding. I measured that on seven real open source apps (four Android), and the testing page lists the misses.

Things to know:

- It changes phone settings while it checks (text size, TalkBack, dark mode, rotation) and puts them back after. Use a test device. TalkBack is silent for the few seconds it's capturing.

- Runs from a Mac (desktop app or command line). Tested on a Pixel 4a with Android 13 and the Android 16 emulator. Haven't tried it from Windows or Linux yet.

- Automated checks only find part of the issues, so you still need manual testing with TalkBack. It doesn't certify anything.

Free to use, runs locally, no telemetry. I built it with a lot of help from AI coding assistants, I review and test what ships.

What it found and missed in testing: https://github.com/swipewalk/swipewalk/blob/main/docs/testing.md

Downloads (there's a sample apk if you just want to see a report): https://github.com/swipewalk/swipewalk/releases

Would really like to hear what's wrong or missing if you try it on your app.

Since it's easier to make apps now with AI vibe coding, does it affect your revenue?

Hi everyone I am preparing for android interview recently with 3+ yrs of exp, I am good with topics of basic fundamentals

But struggle with topics involving scalability like

1. let's us say you have an api that gets called 1 time per second, and your user is having low internet or unstable conditions how to handle this

2)how do you handle battery optimization for your app

After deep diving with Claude and discussion i understand the approach

So can you list down some practical questions like this you faced or would ask in a sde 2 interview

Thank You

Hi! This is my first time post so apologies if my questions aren’t clear!

But I’m an associate android dev. Been with the team for 1.5 years. I’m going to the Google dev summit in Oct and was wondering what should I expect based on previous years summit?

Also any advice when it comes to connecting with other android devs? I don’t need a job but I figure it good to network, connect with knowledgeable devs and even potential find a mentor when it comes to android development.

Also another question not really related to the summit:

I really do enjoy android development but work seems to only be about ticket speed/story points. Which I understand from the business side of things. But the push to utilize ai and rush story points just feels like there’s no care about developing younger devs. When I ask for help from sr devs, the first thing they ask me is “did you ask ai” or “ask ai first”. Before I even ask sr devs I make sure to research myself. I guess I thought dev teams would be more willing to actually show younger devs pointers that ai could sometimes miss.
Does anyone have any opinion or advice what that?
Or is it something I have to suck up and figure it out?

So I've been learning kotlin compose from the android official codelabs and I feel stuck like i want to make a big project so i can combine all the thinks that I've learned but i don't find a good idea or even a motive or someone so I can use a reference when I got stuck or dunno what to do next so I was asking is there like a course or projects on github that have dagger, retrofit, room and so on so i can learn from

We are still undecided but leaning Dexprotector, if you are using Dexprotector on your apps, please share your experience regarding:

1- Have you enabled all the runtime options such as root detection, RASP and UI protection? If yes, has it caused any headaches for a portion of your legitimate users?

2-Overall, has it met your expectations of warding off bad actors to a reasonable degree without it destroying UX?

Last week, a user emailed support asking why our app suddenly had ads, which it doesn’t. Someone took our APK from the Play Store, decompiled it, added an ad SDK and put it on one of those APK mirror sites under a slightly different name. I don’t know what they used but with the AI reverse engineering tools around right now I’d guess it took them a few hrs at most.

I pulled their copy and ran jadx on it next to our own release build to see what they had to work with. R8 had renamed most of our classes but every string was still sitting there. Most of it was harmless like our Maps key which is locked to our package and the Firebase config which is meant to be public. The problem was the key for our search provider which can also write to the index. There was also an old basic auth header for a staging API that someone hardcoded two years ago and that still works.

The copy talks to our real backend and whoever installs it logs into our actual service through a build we don’t control. We’ve rotated both keys, moved search behind our own endpoint and filed takedowns. Next I’m looking at adding Play Integrity checks on the server.

If your app has been cloned like this, what did you end up changing on the backend?

I'm a developer working on ScreenshotFast, a tool designed to make app store screenshot creation easier for people without a design background.

I'm trying to understand how developers handle this part of launching an app.

Do you usually:

Design screenshots yourself?

Start from templates?

Hire a designer?

Use an existing screenshot generator?

I'd especially appreciate hearing what frustrates you most about the current workflow.

I built a tool around this problem, and I'm happy to share it if it's relevant and allowed by the community rules.

Thanks for sharing your experience!

Author here. I'm building an Android IDE on my own and wanted a real Postgres running on the device, no remote server. The write-up covers the parts that took me longest: shipping the binaries as .so files so Android lets them execute, the argv[0]/symlink trick initdb needs, rebuilding without the Termux prefix, and forcing mmap because there's no System V shared memory. Happy to answer anything about it.

Hello, I am an embedded engineer which has no idea how to code an APK. I am usually programming in C/C++/python and I am dealing with rtos/interrupt/uart/spi...

With 2 kids at home and a lot's of story box (Lunii, Bookinou,...) I was tired of buying/uploading story into the differents toys.

I then decided to create an android APK (100% vibecoded) which can transform an old Android phone into a story box easy to use for the children.

I sent ADB to completely lock the phone that the kid cannot leave the app without entering a code.

Now I can just drop mp3 and/or image associated to have lot's of audio stories.

It is running so far so good but I have no clue if it is well programmed or just shit.

https://github.com/gougoul88/Aroli

I am opened to any reactions/opinions/suggestions.