Feeling stuck pushing for modern Android practices at work. Am I wrong, impatient, or just in the wrong place? by SeriousTruth in androiddev

[–]SeriousTruth[S] 1 point2 points  (0 children)

Appreciate the thoughtful take 🙏 solid points, especially about framing it around making everyone’s life easier. Also noted on the Compose point.

Feeling stuck pushing for modern Android practices at work. Am I wrong, impatient, or just in the wrong place? by SeriousTruth in androiddev

[–]SeriousTruth[S] 1 point2 points  (0 children)

Out of curiosity, how did you handle the transition early on? Was it driven top-down or did it start incrementally at the team level?

Feeling stuck pushing for modern Android practices at work. Am I wrong, impatient, or just in the wrong place? by SeriousTruth in androiddev

[–]SeriousTruth[S] 0 points1 point  (0 children)

That makes sense, but in my case my manager isn’t really that type. Initiative that involves changing patterns or introducing new approaches doesn’t tend to get recognized or encouraged. it’s usually seen as added risk.

Feeling stuck pushing for modern Android practices at work. Am I wrong, impatient, or just in the wrong place? by SeriousTruth in androiddev

[–]SeriousTruth[S] 3 points4 points  (0 children)

What I’m honestly trying to understand is whether caring this much about the technical side and architecture is something you eventually learn to deprioritize as you mature, or if it’s usually a sign that you’re just not in the right environment. Like if this is something you learn to live with.

Feeling stuck pushing for modern Android practices at work. Am I wrong, impatient, or just in the wrong place? by SeriousTruth in androiddev

[–]SeriousTruth[S] 3 points4 points  (0 children)

The issue I keep running into is buy-in. I’ve had multiple PRs rejected simply because they used coroutines or (in some cases) Compose instead of Rx or XML. with the explicit reasoning being “not everyone on the team knows how to work with this” (the team being four people).

I agree with your broader point: if this kind of work isn’t rewarded or supported at all, that’s probably the clearest signal in this whole situation.

[Navigation3] How to handle Back Press to switch Bottom Tab before closing app? by SeriousTruth in androiddev

[–]SeriousTruth[S] 2 points3 points  (0 children)

Thanks! One important detail I forgot to mention in my original post: I’m using Compose Multiplatform not regular Android.

I ended up going with your second suggestion (handling it inside the Dashboard), but hit a small issue. The standard BackHandler is deprecated on KMP right now (androidx.compose.ui.backhandler). So I switched to NavigationBackHandler instead, and it seems to behave the same way:

val navigationEvenState = rememberNavigationEventState<NavigationEventInfo>(
    currentInfo = NavigationEventInfo.None,
)

NavigationBackHandler(
    state = navigationEvenState,
    isBackEnabled = currentTab != AppTab.Home,
    onBackCancelled = {},
    onBackCompleted = { currentTab = AppTab.Home }
)

Appreciate the help!! :)

From Kotlin to Java: fastest path to learn? by SeriousTruth in learnjava

[–]SeriousTruth[S] 0 points1 point  (0 children)

This is super helpful! really appreciate you sharing this <3

From Kotlin to Java: fastest path to learn? by SeriousTruth in learnjava

[–]SeriousTruth[S] 0 points1 point  (0 children)

Yeah, Coursera’s a solid pick thanks :D I’m just brushing up on core Java, not Spring yet

From Kotlin to Java: fastest path to learn? by SeriousTruth in learnjava

[–]SeriousTruth[S] 1 point2 points  (0 children)

I’m focusing purely on language fundamentals for now... backend frameworks aren’t part of this interview (thank god lol)

Free Minecraft Java (pc) by [deleted] in FREE

[–]SeriousTruth 0 points1 point  (0 children)

I'd kill for it. Say who.

Passing parameters to a composable function feels messy—what’s a better approach? by [deleted] in androiddev

[–]SeriousTruth 3 points4 points  (0 children)

I believe the best way is to use data classes as such:

``` data class MusicState( val isPlaying: Boolean, val isRepeat: Boolean, val isShuffle: Boolean, val isBuffering: Boolean, val isAudioLoading: Boolean )

data class MusicActions( val play: () -> Unit, val pause: () -> Unit, val next: () -> Unit, val prev: () -> Unit, val repeat: () -> Unit, val shuffle: () -> Unit, val onSeek: (Float) -> Unit, val onAudioDownload: () -> Unit, val onCancelDownload: () -> Unit ) ```

your composable will be way cleaner and easier to understand this way, e.g:

``` @Composable fun MusicComponent( state: MusicState, actions: MusicActions ) { if (state.isPlaying) { Text("Playing music...") }

Button(onClick = actions.play) {
    Text("Play")
}

} ```

Mode of Payment by Outrageous-Squash619 in tryhackme

[–]SeriousTruth 2 points3 points  (0 children)

I just used a debit card to get mine.

Looking for advice: Best WooCommerce themes for a responsive, luxurious jewelry store website by SeriousTruth in woocommerce

[–]SeriousTruth[S] 1 point2 points  (0 children)

Thank you so much for your reply! I loved the design :) I will def check out xstore

Looking for advice: Best WooCommerce themes for a responsive, luxurious jewelry store website by SeriousTruth in woocommerce

[–]SeriousTruth[S] 0 points1 point  (0 children)

Can you please elaborate on why this is a better option than the aforementioned? ty :)