Does developing with Android Studio make a difference in a proposal — does this choice lock me in?

Since Android Studio is the official IDE, new Android versions, target API level requirements, and security patches released by Google every year hit here on day one. With cross-platform systems, you sometimes end up waiting 3-4 months just for community libraries to get updated.

When evaluating the quotes, ask yourself this: Will only Android tablets/rugged handheld terminals be used across your company? If so, Android Studio and native code are hands down the most solid route. But if field reps might want to use their own iPhones tomorrow, a cross-platform architecture solves both sides on a single budget.

Back in 2022, we couldn't find an agency to take over our hybrid-built B2B warehouse app because the original team had used bizarre, deprecated libraries. We had to have it rewritten from scratch in Android Studio and Kotlin; it cost us 160.000 TL and 4 months.

Critical warning: Put a clause in the contract for the "handover of the signing key (keystore/upload key)". The agency might write fantastic code in Android Studio, but if they don't give you that key, you won't be able to update your app on Google Play; you'll be forced to publish an entirely new app from scratch.

edit: I wrote something wrong above, sorry about that.

Yes, native code sets a high standard, but unless your dealer ordering app needs 3D graphics or heavy Bluetooth communication, hybrid tech will do the job just fine. The agency bidding on this might just be pushing native because Android is all they know—definitely question that.

android studio is just software at the end of the day the agency doesn't own it. anyway just set up a gitlab or github account and make sure the code gets pushed to your own repo from day one, that way you won't be trapped with anyone.

Are all of your dealers on Android? Is there any chance you'll take orders from end users outside the company down the road? If so, are you really ready to drop 210 thousand TL on native Android right now and spend just as much on iOS 6 months later?

I feel the same way. The biggest time-waster for us was not knowing who had the final say.

Everyone rushing into android studio development gets stuck at the same point. This is my opinion, I'm not claiming it's absolute truth.

I went through the same thing. If scope grows, either time or budget must grow. There is no third option.

When making decisions, write down the worst-case scenario too, not just the best. Proven by experience.

I agree. Payment schedules should be tied to project phases, not calendar dates.

That's all, sorry if I went on too long.

I'll try it. Solutions that work at a small scale collapse when you grow; I learned this late.

Taking notes for two weeks yields better results than a six-month estimate.

Yes that's exactly how it is with android studio development. Don't hesitate to ask; those who don't ask always pay more.

Taking notes for two weeks yields better results than a six-month estimate.

I don't think this advice fits everyone. When we decide without measuring, we always end up in the same place.

If I were you, I'd go this route.

This thread is archived. The harder it is to reverse a decision, the slower you should make it.

Everyone rushing into android studio development gets stuck at the same point.

Correct in theory, but it doesn't work that way in practice. Code without setup documentation isn't yours, even if you have it.

Weekly written progress reports are much more useful than asking for dates. That's all, sorry if I went on too long.

Let me speak from the other side; I'm on the supplier side. Hasty decisions become decisions you have to fix six months later.

Proven by experience.

Following.

Let me write how it's done in practice. Solutions that work at a small scale collapse when you grow; I learned this late.

If you post the result here it will help others too.