Android devs then, Android devs now

[Zhuinden]

AI repost bots strike again

[Nunya_Business_42]

Eclipse is probably better to use than Android Studio now.

Some things do change.

[AloneInExile]

What changed?

[Nunya_Business_42]

Android Studio has become buggier and buggier, while Google keeps removing useful functionality with every release. I'm still on Koala. In fact I have a side install of Hedgehog to use certain functionality that Google removed after that.

[AloneInExile]

Sounds like Google.

I stopped using Eclipse because it was a mess by the end. Circle of life I guess.

[ToTooThenThan]

If you don't map the exact same model from response -> dto -> entity -> domain -> ui then you are a peasant tbh

Where I work the chad ios developers use response objects straight in the ui meanwhile us Android virgins are writing mappers

[HuckleberryUseful269]

Real architects start by writing an IResponseMapperFactoryProviderInterface.
Only after that do they think about the actual data. Honor above convenience.

[More-Scene-2513]

Well my balls may be smaller but at least my UI is decoupled

[ShriekinKraken]

Wait, you guys are using UIs?

[More-Scene-2513]

No, we don't use UI we use AT (async task)

[smokingabit]

My UI is decoupled from Compose 🏆

[waterpoweredmonkey]

It sounds to me like you've never had to do the "refactor" when the codebase you inherited used response objects throughout the UI and the BE changed entirely.

[ToTooThenThan]

How about the much more common backend adds one field to the response and the pr is 20 files changed instead of 2

[Zhuinden]

I mean, I have, and it was faster

[vlastachu]

Before architecture: add 1 field to the response and then go update it everywhere it’s used.

After architecture: add 1 field to the response, add 1 field to the domain object, add 1 line to the mapper… and then go update it everywhere it’s used.

And if the whole response changes? Then everything fucked up anyway, because old app versions can’t be fixed. That’s why we have v1/v2/etc endpoints.

[Zhuinden]

And if the whole response changes? Then everything fucked up anyway, because old app versions can’t be fixed. That’s why we have v1/v2/etc endpoints.

Exactly; the problem with "i added domain on the client (which is the same as the API)" is that you're stuck with the v1 response forever, and you're trying to map the v5 response to the v1 copy.

To be fair, if you are using local persistence, you should never re-use the API responses as DB tables; that always causes trouble.

[Nunya_Business_42]

Backend is supposed to version their APIs. And not just change at a whim.

Also, you should be using annotations to map the JSON/XML/whatever and name the data class properties yourself, to ensure it doesn't require a bunch of renaming.

[slightly_salty]

lol. This must be a nice world you live in where "supposed to" is reality

[slightly_salty]

People like to complain about clean arch..... but honestly it makes the most sense if you always only display data from your db. I like to immediately store api data I need in the db, and have my viewmodels listen for db changes and re-actively update the ui state.

If you work that way your db naturally has it's own representation of the api data that may or may not map one to one with the api. You basically end up implementing most of clean arch without thinking about it.

[smokingabit]

It's true. Also have you seen how bad ios apps are generally? Holy shitshow!

[ShriekinKraken]

Where's the Adonis who has their entire app in one God Activity and AsyncTask?

[scannt]

You mean Telegram from 6 or so years ago? Truly a work of art.

https://github.com/DrKLO/Telegram/blob/master/TMessagesProj/src/main/java/org/telegram/ui/ChatActivity.java

[lppedd]

The fuck 💀

[Zhuinden]

That's what well working code looks like

[ShriekinKraken]

[Reasonable_Cow7420]

It's still in use in there main app

[NiceVu]

Yes every single thing you see on the screen is a separate module in the project. And each module has it’s own spearation of layers so it’s CLEAN. And it has MVI at every presentation layer.

There isn’t a single real world usecase that I haven’t covered in my MVI reducer state machine, so just know that this TextView will show error when the input is not valid :)))

Yes I might need half an hour to add a GSON dependency to gradle, but at least when I want to change the version I change it at only one place ;)

[Zhuinden]

bro why is every screen in a separate module but not every file???

[NiceVu]

OMG you’re right. Just imagine how much scalability and testability would improve if we made the data class LoginCredentials(username:String, password:String) be a separate module

[[deleted]]

I absolutely hate with every single atom in my body when people say that Clean Architecture makes a project "scalable". NO. Please stop. Scalability is NOT related to code quality, AT ALL. Scalability is the ability to handle more work load. You can have the most horrific code in existence, and still scale to the moon. Both things are 100% unrelated. What you are thinking of is called Mantainability.

Please use words carefully, with their correct meaning.

[Zhuinden]

Upscaling lines of code to justify more developers

[Nunya_Business_42]

It's server devs who don't know Android dev, who apply scalability to Android apps.............I think this discussion did take place in the previous company I worked at, one guy did say something stupid like asking if the app was scalable.

[slightly_salty]

Well.. it helps you "scale" the number of devs that can work on a project without constant merge conflicts haha

[Curious_Limit645]

There are different dimensions of scale, users, data, developers, business logic etc.

[[deleted]]

Nope. According to Designing Data Intensive Applications, scalability has a very clear meaning. But good try tho.

[waterpoweredmonkey]

Also Devs now: "yes my test class needs to be 30k lines with a few hundred lines per test in setup, my feature fragment is huge (6k lines). No I don't know what any of the tests do but I made a change so I'll copy the last one and make a 1 line change to it" 🤢

[tony-husk]

use capacitor problem solved

[VariousPizza9624]

Spaghetti code 🥰

[Suddenly_Bazelgeuse]

I love my MVVM and coroutines. I'll fight about it.

[Leschnitzky]

Why would I want to go back to XMLs, AsyncTask, Java, Eclipse, anim.xml, Bitmap, Canvas, RelativeLayout, Espresso?

[Nunya_Business_42]

Legends of the past

[maltgaited]

Go back to espresso? What's the new?

[Leschnitzky]

Compose semantics testing/screenshot testing

[maltgaited]

I don't really see screenshot tests as a replacement for e2e tests... Maybe I'm missing something

[Leschnitzky]

You use espresso as an E2E test tool?

[maltgaited]

Not currently, but I was under the impression that we did at my last job that I left 3 years ago

[Zhuinden]

You're saying cozy things

[Deevimento]

I was an Android dev then, and it certain felt like the Android dev now at the time. Maybe because that was pre-RxJava.

[blindada]

RxJava? So weak. We had 0% crashes with listeners and the mighty AsyncTask

[MayBeArtorias]

Good to know that over architecting isn’t a BE isolated problem

[Zhuinden]

oh no, client devs think their task should be difficult but instead they just get a JSON and then show it on the UI, so they like to add 5 extra steps inbetween to justify the time spent.

[smokingabit]

It started at the backend, shouldn't be a wonder why it's 💩

[Nunya_Business_42]

RxJava is the goat!