hello, Ivano!@

(give or take a @)

how can I help you today?

ehy Mark to you and your secret Dragon Lair, as i read for the last transcriptions really nice discussion last time. Well I am still busy between testing, cool libraries and kotlin, but maybe you can help me on that. Android has context

is correct to say that context in some way is useful way to pass the android logic in other classes?

um

a lot of software architects have serious issues with the whole Context thing

I mean I pass into a contructor context and in this way I can split a class in more part calling some methods in one and others in another one to...

not violate the single repsonsibility concept, the cohesion of the member variables with his methods

in more pragmatic words

if you are asking whether decomposing classes into separate ones is a good thing, then yes

if anything, Context seriously violates the single responsibility concept

i do not get

Context is kinda of like Object in Java

Android's Context is a great example of a "God object": https://en.wikipedia.org/wiki/God_object

exactly

great glad you agree with me

I am really into MVP

now, in Google's defense, the Android, Inc. team started work in this in the 2004-2005 timeframe, IIRC

and I have a lot of doubt if I should divide for features the class

packages*

I cannot really answer that

interesting so I should kind of follow Uncle Bob, trying to find as much as dependency injection possible

all else being equal, smaller, more-focused classes are better than bigger ones

however, all else is rarely equal

to put on the center of the Bob ball pure and abstract java no android code

having a pure-Java module in an Android project can be useful

for junit testing

and also all this use of interfaces

sometimes it looks to me a bad idea to make communicate a presenter with a view by mean of an interface

the code is less readable,

my general rule is to use interfaces or abstract classes where there is a 1:N or M:N relationship between classes

?

I don't use interfaces just for the sake of having interfaces

ah ah

if there will be N implementations of the interface or abstract class, and so there is real polymorphism going on, then they're fine

aaah i see

one thing to bear in mind, though, is that a lot of Java advice is really aimed at server-side Java, where you have lots more heap space and such

ah

is undestandable

sometimes, we have to make software architecture sacrifices to allow our apps to run acceptably well on low-end phones

server should have more memory i guess

is something i cannot catch

what is the necessity to cover android 1

in 2016

if you mean the Android One line of phones, I do not know how well those sol

er, sold

however, there are plenty of other low-end Android phones that are not officially part of Android One

particularly if you are distributing through more channels than the Play Store

i mean android donut

1.6

oh, I haven't really considered 1.6 to be worth worrying about in a couple of years, at least

i see

again, it depends a bit on your distribution channels

sure

with the Play Store, we get good metrics, both overall (monthly device dashboards) and for your own apps

true

other channels might reach more people with seriously old phones, but we might not have the data to justify it

but trying to get a modern Android app to support 1.6 would be *painful*

definetely

just think over memory exception, or animation not implemented

anyay the second thing i cannot understand in the open source android community is over documentation, there are all these important libraries,

that make testing easier and are the standard de facto today, but

the second versions usually do not have documentation, enough documentation

and the method names change a lot....

so that become really difficult to use the second version of these libraries ( ex rxjava2) if you do not know well rxjava1 but

I am not quite certain what your question is, sorry

ok

thanks Mark and have a nice evening

you too!

the next chat will be next year

more specifically, Tuesday at 9am US Eastern

have a nice year eve bye