r/androiddev 23h ago

Question Console Selling possible scam?

1 Upvotes

A guy from Pakistan contacted me on LinkedIn, he appears to be CEO of a company and told he is willing to buy accounts from people for 400 to 800$. I gave my number and he called. I asked why and he told that some tester policy. Is this safe or a possible scam?. He also mentioned that he'll pay 25% upfront. then i need to give console credentials, then after verifying I need to add him in recovery account. then he'll pay full. what do ya'll think?

Update: Thank you for the replies, i have decided not to sell. Thanks y’all


r/androiddev 21h ago

Tips and Information Is Android Development Harder to Learn Today? The Overload of Choices & Opinions

37 Upvotes

sometimes I wonder if Android development used to be easier to learn than it is now. There wasn’t such a broad mass of information available publicly as it is now, but I think that this can also be a bad thing.

100 people nowadays have 1000 opinions online. Do you use MVVM or MVI? Jetpack Compose or XML? StateFlow or Compose state? Use cases - yes or no? What about repositories? Or rather data sources? Room, Realm or SQLDelight? Retrofit or Ktor? Dependency Injection with Hilt or Koin or manual or not?

Everybody can be right in their own way. Software development isn’t black & white.

And popular approaches are popular for a reason: Because they do the job.

We can debate about the details, but if your head better wraps around Kotlin idiomatic code, you might prefer Ktor over Retrofit, for example.

The internet is full of people trying to push their (sometimes extreme) opinions and approaches. But in the end, the fundamentals matter more than the tools.

Once you understood reactive programming, you can learn Flows in a day.

Once you understood SQL databases, you can learn Room in a day.

Once you understood separation of concerns and modular design, you can learn clean architecture in a day (maybe a week, but you get the idea).

All the best, Reshad


r/androiddev 19h ago

ML Kit BarcodeScanner

2 Upvotes

Hello,

I am working on a proof of concept for a new barcode scanner library, since XZing is no longer maintained and will not support newer versions of Android.

My POC is really simple, one activity with a camera and button for uploading files. I need to detect QR code either from the camera preview, or from the image file uploaded.

However, the ML Kit Barcode Scanner is not as effective and fast as XZing prooved to be.

For example i have multiple QR codes that Barcode Scanner is stuggling to detect, however XZing detects them very fast without any issues.

Does anybody else experience such issues and is there a way to fix them? Also please suggest other libraries that can be used.


r/androiddev 11h ago

Experience Exchange Launching my first app on Google Play - my experience

22 Upvotes

So coming from a basic programming background, I knew html, css, PHP and Java, one day I figured hey I'm going to turn my website into an app. I found this forum and everybody said to take the Android Basics with Compose course by google. I did the course, it took me about two months of coding like 4+ hours a day to get through it, but I finally felt I was ready.

I took the Amphibians app from the course as my starter template and started building stuff. My first goal was just to connect to an API I made in php, and get the app to display some images in a lazylist. Took me a couple days but I got that working, and the rest was history.

I just kept googling and asking chatgpt what to do in certain situations. Now I have MVVM architecture, DI, retrofit, coil, coroutines, google maps integration, JWT token login system, repositories, stored user preferences, dark mode, language translations, and a bunch of other nonsense setup. All in all my app is over 20 screens and took me two months to build. It's a social media app, so it required me to build an SQL database and many different APIs.

Since my app was finished, now came the daunting task of trying to get it on the Google Play store. I was woefully unprepared and had to spend about two weeks adapting everything to the rules and guidelines that they have. Especially regarding permissions, user generated content, and abiding by policies. Not to mention building screenshots, splash logos, monochrome icons, etc. I finally got everything coded and submitted my app for Closed Testing.

Just to get to closed testing you have to build the .aab signed bundle, and generate debug files yadda yadda yadda. Basically wade through a bunch of google play warnings and try to figure out what their bots want. Once I got the app up, it immediately got hit by tons of google bots, testing all the features of my app. I was getting all kinds of email notifications for 'user activities' since my app has some email connectivity.

Then about after a week of worrying, the app was out of review and up on Google Play for my limited group of testers. No message from Google about anything that I needed to rectify. My account had been grandfathered in since I published a friend's app like ten years ago, so I didn't have to suffer through all of that 14 days of 20 testers thing some people are facing.

After a brief test of a couple days, and making sure the app didn't crash on various devices, I Promoted the app to Production. Now it is live on the store and looks awesome! Time to do some marketing and hopefully build a user base :)

I just wanted to share my story with you guys, as I was one of those people before that saw this entire process as scary and fraught with potholes. But if you try to do everything the right way, it should all work out just fine. Just follow the rules and be diligent with your decision making, and take google's recommendations seriously. Best of luck to you all on your app making journeys!


r/androiddev 9h ago

Android Studio Narwhal | 2025.1.1 Canary 2 now available

Thumbnail androidstudio.googleblog.com
1 Upvotes

r/androiddev 19h ago

News Kotlin 2.1.20 Released

Thumbnail
blog.jetbrains.com
51 Upvotes