All bites
The whole library, newest first. Filter by what you are here for, or pick a topic if you already know.
4330 bites
Page 62
Platform-specific typography in a global theme
Define one theme with Platform.select for fontFamily, expose semantic text styles, and reuse them everywhere rather than per-screen overrides.
Unifying divergent native video player props
A JS component accepts a unified source prop, then uses Platform.OS to map it into each native view's expected props before rendering.
Offline data storage and sync strategy
Persist locally in SQLite or WatermelonDB, queue mutations with a pending flag, detect reconnection with NetInfo, then replay the queue and resolve conflicts.
Creating a native module with a sync method
Extend the RN base class, mark the method exported and synchronous, register in a package or bridging file.
Purpose of RCTBridgeModule and ReactContextBaseJavaModule
These declare a class as a discoverable native module, provide the JS-facing name, and let RN export methods to JavaScript.
Threading of native module methods
Methods run on a dedicated native module queue, not the UI thread; long blocking work stalls other module calls; offload to a background executor or override methodQueue, returning results via promise.
TurboModules and lazy loading benefits
TurboModules use JSI for direct, synchronous, type-safe calls and are loaded lazily on first use instead of all at startup, cutting init time.
What JSI is and how it replaces the Bridge
JSI is a lightweight C++ layer letting JS hold references to native host objects and call them directly and synchronously, with no JSON serialization or async batched queue.
TurboModule lazy loading vs eager startup
Legacy modules are instantiated eagerly at launch; TurboModules initialize only when JS first accesses them, so unused modules cost nothing at startup.
Fabric UI update lifecycle vs old architecture
Render builds an immutable C++ shadow tree, commit diffs trees and runs Yoga layout, mount applies mutations to native views; JSI shares the tree, enabling synchronous and concurrent rendering unlike the…
Generating a signed release APK or AAB
Create a keystore, reference its credentials via gradle.properties (gitignored), wire a release signingConfig in build.gradle, then assembleRelease or bundleRelease.

What counter metrics track health of weekly active users?
Tests whether you can spot growth-at-all-costs blind spots. A strong answer pairs WAU with 7-day retention, sessions per user, and error rate, mapping each to churn, shallow engagement, or bugginess.

How do you instrument a marketing funnel versus a product-led growth loop?
This tests if you distinguish linear attribution from compounding systems. A strong answer contrasts stage-tracking and CAC with viral-coefficient instrumentation, cycle-time velocity, plus identity resolution.

What fields belong in an experiment tracking event?
Tests disciplined schema thinking over random fields. Strong answers cite a tracking plan with event and user properties, environment separation, and consistency. Red flag: dumping data without a schema or single source of truth.

Describe RICE scoring and architect data pipelines for Reach and Effort
Define RICE; automate Reach via event streams with time windows; automate Effort from PM tool estimates with calibration.

How do you design allocation logic to minimize concurrent A/B test interactions?
Compare mutual exclusion with layered randomization via layers and reservations; stress isolation vs throughput.
How would you structure an event schema for funnel and cohort analysis?
This tests analytical event modeling. Use an immutable log with one row per event; attach context user_id, session_id, campaign; use a wide atomic table plus extensible contexts for funnel and cohort queries without joins.

How would you architect long-term holdback experiment groups?
Tests longitudinal causal inference and engineering tradeoffs for multi-month isolation. A strong answer covers bucketing, delayed metrics, and cross-experiment guards. Red flag: daily re-randomization or ignoring survivorship bias in aging cohorts.
Architect an experimentation dashboard for culture
Searchable experiment repository, structured hypotheses, results regardless of outcome, and cross-team discovery.
How do you attribute signups to Facebook, Google, and blog campaigns?
This tests URL-based campaign attribution and session persistence. A strong answer covers UTM tags, landing page parsing, cookie storage, and writing the source to the user record at signup.