Sponsored by

Find leads on Reddit on auto pilot

Topic: android

43 skills in this topic.

find-missing-translations Use when comparing Android strings.xml locale files to find untranslated string resources, missing translation keys, or preparing translation work for a specific language
vitorpamplona/amethyst 1,494
android-expert
vitorpamplona/amethyst 1,494
compose-expert Advanced Compose Multiplatform UI patterns for shared composables. Use when working with visual UI components, state management patterns (remember, derivedStateOf, produceState), recomposition optimization (@Stable/@Immutable visual usage), Material3 theming, custom ImageVector icons, or determining whether to share UI in commonMain vs keep platform-specific. Delegates navigation to android-expert/desktop-expert. Complements kotlin-expert (handles Kotlin language aspects of state/annotations).
vitorpamplona/amethyst 1,494
desktop-expert
vitorpamplona/amethyst 1,494
find-non-lambda-logs Use when auditing or migrating Log calls to lambda overloads, after adding new logging, or checking for string interpolation in Log.d/i/w/e calls that waste allocations when the log level is filtered out
vitorpamplona/amethyst 1,494
gradle-expert
vitorpamplona/amethyst 1,494
kotlin-coroutines
vitorpamplona/amethyst 1,494
kotlin-expert
vitorpamplona/amethyst 1,494
kotlin-multiplatform Platform abstraction decision-making for Amethyst KMP project. Guides when to abstract vs keep platform-specific, source set placement (commonMain, jvmAndroid, platform-specific), expect/actual patterns. Covers primary targets (Android, JVM/Desktop, iOS) with web/wasm future considerations. Integrates with gradle-expert for dependency issues. Triggers on: abstraction decisions ("should I share this?"), source set placement questions, expect/actual creation, build.gradle.kts work, incorrect placement detection, KMP dependency suggestions.
vitorpamplona/amethyst 1,494
nostr-expert
vitorpamplona/amethyst 1,494
quartz-integration
vitorpamplona/amethyst 1,494
crash-instrumentation Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
nexus-labs-automation/mobile-observability 108
user-journey-tracking Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
nexus-labs-automation/mobile-observability 108
symbolication-setup Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
nexus-labs-automation/mobile-observability 108
session-replay Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
nexus-labs-automation/mobile-observability 108
network-tracing Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
nexus-labs-automation/mobile-observability 108
navigation-latency Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
nexus-labs-automation/mobile-observability 108
interaction-latency Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
nexus-labs-automation/mobile-observability 108
instrumentation-planning Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
nexus-labs-automation/mobile-observability 108