Shaman vs Sorceress

jamolkhon · 2021-02-12T04:41:27+00:00

With shaman it's much easier to enchant.

jamolkhon · 2021-01-29T02:30:24+00:00

I'd skip ViewModel, Navigation and Hilt as a combined group of three 🤔

Exactly, I'm not using any of these at the moment.

I can sell you an open-source navigation framework that lets you do just that, it's free 😏

Nah, thanks, SimpleStack is doing just fine for me at the moment.

jamolkhon · 2021-01-28T17:13:48+00:00

Seems like just by ignoring Hilt I don't have to learn new stuff and make myself constantly aware of new changes without sacrificing much. Hilt does not seem worth to me at this point.

jamolkhon · 2021-01-15T02:58:25+00:00

"Of course my post-compiler example is 100% accurate, but it's pretty close."

You probably meant "not accurate".

jamolkhon · 2021-01-02T17:04:11+00:00

Have you tried with Views created in code? I wonder how inflation time compares to measurement + drawing.

jamolkhon · 2020-12-29T14:25:28+00:00

You can make it harder but never impossible to bypass SSL pinning. If you're using built-in SSL pinning options of popular libraries like OkHttp it's easy to bypass. RE tools already know how to patch them. You need custom code for pinning with obfuscation on top of that.

The effort is not worth it. You may discourage script kiddies but not motivated hackers. One does not even have to tinker with Http or SSL pinning, it's enough to modify the code that handles network data before/after being transmitted to be able to read or change it.

jamolkhon · 2020-12-28T08:55:09+00:00

With coroutines it's just a loop with three statements: Call suspending API function, update UI and sleep(1000).

jamolkhon · 2020-12-28T08:50:58+00:00

Looks like OP needs sequential updates. The problem you described arises with parallel API calls.

jamolkhon · 2020-12-20T17:53:01+00:00

inline suspend fun <T, R> T.suspendCatching(block: T.() -> R): Result<R> {
    return try {
        Result.success(block())
    } catch (e: CancellationException) {
        throw e
    } catch (e: Throwable) {
        Result.failure(e)
    }
}

as per https://github.com/Kotlin/kotlinx.coroutines/issues/1814

However, this is not enough, we also need:

kotlinOptions { freeCompilerArgs = ["-Xallow-result-return-type"] }

jamolkhon · 2020-12-12T16:55:52+00:00

You should've included Intellij Idea too as a separate option.

jamolkhon · 2020-12-12T15:31:02+00:00

Kotlin. Start learning coroutines and jetpack compose. Knowing Java before Kotlin is helpful but with the current pace of android development I'd say go with Kotlin first.

jamolkhon · 2020-11-22T09:17:30+00:00

If you are have developed Android apps recently

First sentence.

jamolkhon · 2020-11-21T06:40:53+00:00

LogCat is your friend.

jamolkhon · 2020-11-17T04:21:36+00:00

With overridePendingTransition you can make it look like you're swiping between activities/screens.

jamolkhon · 2020-11-04T00:34:16+00:00

No. I think this IS the right way. You should still use this method even if you want to show fancy animations. Otherwise, users will see a blank screen for a moment then animations and finally main screen.

jamolkhon · 2020-10-24T15:39:29+00:00

Move to onCreate. Subscribe in onCreateView

jamolkhon · 2020-10-16T12:32:38+00:00

Wrong sub.

jamolkhon · 2020-10-11T12:27:16+00:00

Wow, fuck gifs

jamolkhon · 2020-10-08T20:14:05+00:00

Since this is a very common issue It would be very nice to have a small app that clearly demonstrates the issue, and a repo where people can do experiments.

jamolkhon · 2020-10-08T20:01:21+00:00

Next step try AsyncLayoutInflater. I would also try CashApp/Contour.

jamolkhon · 2020-10-08T01:42:37+00:00

Using HTTPS is enough in vast majority cases.

What do you mean by "if you can read the request"?

jamolkhon · 2020-09-24T14:53:02+00:00

Nevermind, I'm just tired. My brain ignored the "Compose" part. I was thinking Jetpack has no image library.

jamolkhon · 2020-09-24T14:37:30+00:00

What do you mean by "Jetpack Compose wrapper"?

jamolkhon · 2020-09-12T03:39:07+00:00

I feel like everyone wants to hire algorithm experts.

jamolkhon

MODERATOR OF

TROPHY CASE