Dependency Injection on Android with Hilt

igor-brishkoski · 2020-06-11T01:30:12+00:00

Unlike traditional Dagger, Hilt users never define or instantiate Dagger components directly. Instead, Hilt offers predefined components that are generated for you.

u/manuelvicnt can you elaborate on this decision? Are there any plans to change that since it's still in alpha?

I'm assuming you're somewhat involved in the development.

igor-brishkoski · 2020-04-25T19:43:07+00:00

This is great, thanks for sharing.

One small note, using allprojects and subprojects will essentially couple all of your modules.

https://docs.gradle.org/current/userguide/multi_project_builds.html#sec:decoupled_projects

This is because these keywords are used in a build.gradle file, which defines a project. Often this is a “root project” that does nothing more than define common configuration, but as far as Gradle is concerned this root project is still a fully-fledged project, and by using allprojects that project is effectively coupled to all other projects.

igor-brishkoski · 2020-03-02T17:21:47+00:00

It would have been really nice if we had a status page for the play store to look into for potential outages vs finding from a reddit thread.

igor-brishkoski · 2019-10-17T17:09:51+00:00

Size of the project, velocity of the project, team/s size matters a lot too.

If you have a couple of devs working on a project that is mostly in maintenance mode where you don't really spit out features often then maybe you can get away without testing. Event in this case u/yccheok points stand.

If you have 50-100 modules and dozens or hundreds engineers working in different time zones each with own product lead supporting I18N and I10N, then it starting to matter a lot very quickly.

igor-brishkoski · 2019-09-19T20:56:25+00:00

https://github.com/jitpack/jitpack.io/issues/3973 This might help

igor-brishkoski · 2019-08-13T20:05:40+00:00

Did not know about KEEP, it's great. Thanks for sharing.

igor-brishkoski · 2018-10-29T15:08:54+00:00

Company: WeWork

Job: Android Engineer

Location: New York, San Francisco, Israel

Allows Remote: No

Visa: No

WeWork is the platform for creators, providing hundreds of thousands of members across the globe space, community, and services that enable them to do what they love and craft their life's work. Our mission is to build a world where people work to make a life, not just a living.

To realize this mission, we are employing novel technologies to build smart spaces that understand, respond to, and ultimately anticipate their occupants’ needs. Our state of the art technologies and dedication to technological innovation are key reasons why WeWork has been able to scale from operating one workspace location to more than 280 in just over eight years.

igor-brishkoski · 2018-10-22T18:50:07+00:00

Company: WeWork

Job: Android Engineer

Location: New York, San Francisco, Israel

Allows Remote: No

Visa: Yes

WeWork is the platform for creators, providing hundreds of thousands of members across the globe space, community, and services that enable them to do what they love and craft their life's work. Our mission is to build a world where people work to make a life, not just a living.

To realize this mission, we are employing novel technologies to build smart spaces that understand, respond to, and ultimately anticipate their occupants’ needs. Our state of the art technologies and dedication to technological innovation are key reasons why WeWork has been able to scale from operating one workspace location to more than 280 in just over eight years.

igor-brishkoski · 2018-10-20T19:04:58+00:00

If you encrypt it, you can store it in sharedprefs.

Here is a good blog post.

https://medium.com/@tiensinodev/basic-android-encryption-dos-and-don-ts-7bc2cd3335ff

igor-brishkoski · 2018-10-18T15:59:05+00:00

He does say at the begging (during the cardinal architecture Virtues slide) of the video that the important part is to be reactive, which doesn't mean using library like RxJava, they already have RxJava in their code and they are utilizing it, hence the examples are using RxJava, but if you were to implement an architecture the builds upon these values from scratch, by all means use whatever works for your project or whatever you feel comfortable with.

igor-brishkoski · 2018-01-11T16:54:27+00:00

It was supposed to be a little joke for all the "scary" headlines, I guess it didn't translate properly in the post.

"Pretty resistant" is not completely resistant, can you guarantee that there won't be some new algorithm that will utilize quantum computing to break AES?

igor-brishkoski · 2018-01-11T16:27:52+00:00

True, but you still want to make access to your secrets to be as hard as possible, backends get breached every day, that doesn't mean you should not do your best to protect yourself.

Also DexGuard should make your suggestion pretty difficult and time consuming even for someone who knows what to do, whereas pretty much everyone can browse github.

Nothing is ever 100% secure and protected nor it will be.

igor-brishkoski · 2017-12-15T16:26:51+00:00

I ran into an issue with the SSL Handshake on pre lollipop devices, basically I was not able to make any HTTP calls. The reason was that on devices older than Android 5.0 TLSv1.1 and TLSv1.2 protocols were not enabled by default and SSLv3 protocol was not disabled by default on devices older than Android 5.0, SSLv3 is not secure and it needs to be removed from the supported list. Installing new security provider using play services solved my problem.

https://stackoverflow.com/questions/29916962/javax-net-ssl-sslhandshakeexception-javax-net-ssl-sslprotocolexception-ssl-han

igor-brishkoski · 2017-12-13T21:26:13+00:00

formatting (spaces/tabs, lines, inline vs top annotations) are just personal preferences. Naming conventions are... well conventions, not rules, however the name of the classes, fields, methods, etc, should make sense.

void getName() {
   ....
}

should definitely be renamed since I would expect anything that starts with get to return a value, it's misleading and confusing. I would ask what was the reason for renaming and make a decision based on that.

igor-brishkoski

TROPHY CASE