For context I have more than 6 years of experience in React Native in both startups and big tech across multiple industries and have delivered 5M+ user apps and have scaled from 0–>1 as well.
I’ve been unemployed for more than 6 months now and its the first time for me to go without a job this long, I get interviews however and even in the interviews I get told that this was an amazing interview later I get ghosted or the offer is retracted.
I wanted to ask if there are people who are also in a similar position? If you have made it to the other side what were the key pointers that helped you land an offer? Because I’m incredibly frustrated as to how to go about things now.
I maintain ExecBro, an MCP server that lets AI agents debug React Native apps (logs, network, screenshots, taps, component tree). It used to be called react-native-ai-devtools.
Looking at the anonymous usage numbers this week, I found that of the roughly 280 installs that used it in the last 30 days, 88 were on a version from before June, and 81 of those were on 1.4.15, a release from April. That's almost a third of everyone using it.
The current version is 2.26.4. They didn't choose to stay there: the old setup instructions said to run `npx react-native-ai-devtools`, and npx keeps reusing the copy it downloaded the first time, without ever checking for a newer one. That was my mistake in the docs, and it means everyone who set it up that way has been stuck since the day they installed it.
If your MCP config has `npx react-native-ai-devtools` or `npx execbro` without `@latest`, this is you.
The fix for Claude Code:
claude mcp remove rn-debugger
claude mcp add execbro --scope user -- npx -y execbro@latest
(`rn-debugger` was the name the old instructions used. If you named it something else, remove that one instead.)
For Codex:
codex mcp add execbro -- npx -y execbro@latest
For Cursor, Windsurf and other clients that use a JSON config, change the command to:
"command": "npx",
"args": ["-y", "execbro@latest"]
Then restart your client. With `@latest`, npx checks for a new version every time the server starts, so this won't happen again. Starting with the next release, ExecBro will also tell your agent when it's out of date, so you'll hear about it instead of finding out by accident.
Since April it has gained Electron app support, physical iPhone support, credential redaction in logs and network output, a lot of work on tap reliability, and a long list of fixes, so it's a noticeably different tool.
It's free to use and the core is MIT-licensed: github. If something broke for you on the old version and put you off, I'd like to hear what it was.
v0.4.0 came out this week. It adds `lazymobile dev` for Metro, app launch and stop, and log filters.
Running a React Native app means juggling a simulator, an emulator, adb reverse for Metro, the dev menu and logcat. lazymobile puts them in one terminal dashboard.
- One list of iOS simulators, Android emulators and connected phones. Boot, cold boot, erase and create them.
- `lazymobile dev`: forward Metro's port (8081), open the developer menu and reload the app, on an Android emulator or phone.
- Live logs per app, followed across restarts, with filters, saved presets and crashes marked in red.
- In an Expo project: list EAS builds, install a finished build on a running simulator or emulator, start and cancel builds.
- Run your own project commands from a .lazymobile.json on the selected device. It shows the exact command and asks first.
- The same features as plain commands with --json, for scripts and coding agents.
Free and open source (MIT). The developer menu and reload only work on Android for now. Which part of your daily run, build and debug loop still has you leaving the terminal?
If you have ever tried adding iOS Live Activities (Dynamic Island) or Interactive Home Screen Widgets to a React Native or Expo app, you probably know the pain:
You have to write and maintain Swift/SwiftUI for iOS and Kotlin/RemoteViews for Android.
Handling 2-way interactivity without launching the full app is tricky (especially AppIntents on iOS 17+ and PendingIntents on Android).
Android widget touch areas get misaligned due to launcher letterboxing / aspect ratio scaling.
Keeping timers running on Lock Screen usually drains battery if not backed by native OS hardware chronometers.
To fix this for my own projects, I spent the last few months building react-native-live-widgets (v1.2.3) — an end-to-end declarative widget engine for React Native and Expo.
🚀 What it does:
100% TypeScript & JSX: Write your widget layout just like standard React components (<VStack>, <HStack>, <Text>, <Progress>, <Button>, etc.). Zero Swift or Kotlin knowledge needed.
Dynamic Island & Live Activities: Native expanded, compact leading/trailing, minimal, and lock screen presentations with real-time push update support.
Pixel-Exact Touch Layer (v1.2+): On Android, it replaces rigid grid overlays with a dynamic rn_hit_layer that auto-compensates for fitCenter letterboxing — buttons and checkboxes register clicks with 100% precision.
Zero-Battery Hardware Timers: Direct integration with system hardware clocks (UI.Timer on iOS and native android.widget.Chronometer on Android). It ticks down smoothly without waking up the JavaScript thread or draining battery.
2-Way React Hook: Handle widget clicks inside your React Native JS runtime seamlessly with useWidgetAction((actionId, payload) => ...).
Background Remote Sync: Fetch JSON updates from your backend even when the app is force-killed via Widget.setRemoteConfig().
Swift 6 & iOS 18 Ready: Compiled with Xcode 16 Swift 6 strict concurrency compatibility.
Automatic String Catalog Linking: Auto-generates and links Localizable.xcstrings and res/values-*/strings.xml for full multi-language Widget Gallery support.
All-in-One CLI Setup: Run npx react-native-live-widgets init to auto-configure iOS WidgetKit extension targets and Android Widget providers in seconds (supports Expo Config Plugins & Bare RN).
💻 Quick Example:
tsximport React from 'react';
import { Widget, VStack, HStack, Text, Button, Timer } from 'react-native-live-widgets';
export const DeliveryWidget = () => (
<VStack padding={14} backgroundColor="#0F172A" cornerRadius={16}>
<HStack justifyContent="space-between" alignItems="center">
<Text typography="headline" color="#38BDF8">Order On The Way 🛵</Text>
<Timer targetTimestamp={Date.now() + 15 * 60 * 1000} color="#F59E0B" isCountdown />
</HStack>
<Text typography="caption1" color="#94A3B8">Driver is 1.2 km away</Text>
<Button
title="Contact Driver"
actionId="CALL_DRIVER"
backgroundColor="#2563EB"
color="#FFFFFF"
/>
</VStack>
);
// Register widget
Widget.register('DeliveryWidget', DeliveryWidget);
🌐 Links & Try it out:
Interactive In-Browser Live Simulator: Web Demo (You can test Dynamic Island stretching, equalizer audio waves, and widget clicks directly in your web browser)
I shipped a sudoku game with live 1v1 duels to both stores, built solo with Expo. Some notes that might help anyone doing real-time features without a dedicated game server.
Architecture
Expo / React Native with Expo Router, SQLite for local games, a small kv store for the active game.
Moves go through a Cloud Function. Clients never write to the battle state; each move is a callable that checks it against the solution, counts mistakes and updates the shared state. Slower than peer-to-peer, but cheating is basically off the table.
Live state in Realtime Database, clients subscribe to it. Fine latency for a game where a move every few seconds is normal.
Rating: plain Elo with K=32, seasons of four months, and at season end everyone's rating moves halfway back to the start.
The empty lobby problem
With a small player base, quick match often finds nobody. I record every finished match as a list of timestamped events (positive = correct cell, negative = mistake). When nobody joins within a few seconds, the server picks a recorded match at a similar rating and difficulty, scales it to the new puzzle's blank count and replays it. The bot doesn't "solve" anything, the server just reveals events as time passes. It plays like a human because it was one, hesitation and mistakes included.
Difficulty grading
The generator rates each puzzle with a technique-based solver (naked/hidden singles, pointing pairs, box/line, naked triples, X-Wing, Swordfish, XY-Wing) instead of counting clues. The hardest technique needed decides the level.
Things I'd do differently
Put anything that affects ranking behind a server call from day one. Retrofitting validation is painful.
Keep native modules minimal: every one means a new store build instead of an OTA update.
Happy to go deeper on any part. If you want to see it running: Android · iOS