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 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
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 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.
After my breakup, I started journaling about my everyday life, using whatever journaling apps I could find on the App Store.
Then one day, a thought crossed my mind: What if I could turn my journal entries into visual stories? Imagine reliving your memories as a retro comic, an anime, a manga, or even a cartoon.
That's how SoloSaga was born — a journaling app I vibe-coded a few months ago.
I wanted the entire experience to feel like you're the protagonist of your own story.
I went with a neo-brutalist design to complement the comic panels. I even added narration using ElevenLabs voices, inspired by those dramatic narrators you hear in anime.
But I didn't want to stop at just generating comics.
Here's what else I built:
Characters: Customize your own character and create separate character profiles for the people in your life.
Chapters: Each journal entry becomes a chapter in your story.
Story Arcs: Every month becomes a new story arc, with a dedicated section to revisit your journey and discover insights about your life.
Nova: An AI companion that knows about your day. You can talk to it about your thoughts, feelings, or whatever is on your mind. It's there for emotional support, not to solve your coding problems.
The essentials: Light and dark modes, customizable journaling reminders, and more.
The idea behind SoloSaga is simple: instead of just documenting your life, why not experience it as a story where you're the main character?
I've open-sourced Open Arcade, a set of six canvas mini-games in a handheld-console UI. It comes with u/open-arcade/react-native, a WebView host that talks to the page over a small typed bridge.
Swipe between four tiny worlds. The object turns and reshapes as the selected world changes.
The React Native implementation draws the worlds in one Skia runtime shader.
Building the shapes: each world is a signed-distance scene. The shader combines spheres, rounded discs and other shapes to create the cloud planet, racing planet, burger and arena. The artwork is drawn in code.
Morphing between worlds: the shader blends the distance fields of the current and next world using a morph parameter. Rotation and squash are separate parameters, so the transition can turn and deform at the same time.
Driving the shader: Reanimated shared values supply the motion state. A derived value packages the current parameters as shader uniforms, and Gesture Handler supplies the pan interaction.
Lighting: the shader shades the result with key light, fill, a rim highlight and ambient occlusion from the distance field.
Reduced Motion: idle spin is disabled when the preference is enabled.
The attached clip is a motion preview; these notes describe the React Native implementation.
Built with Expo (@expo), React Native Skia, Reanimated and Gesture Handler. Thanks to Software Mansion and William Candillon.
Last month I pushed an update that broke onboarding on some android devices and didn’t find out for days. Nobody emailed me, I just noticed signups dropped and I only track total signups so I couldn’t see where people were falling off.
I’m a solo founder with around 5k users, shipping most weeks through EAS. My whole QA is a checklist in my notes app that I run on my iphone and one old android. It only covers what I remember to check on devices I own and the bugs are always on some samsung or xiaomi I’ve never touched.
I tried automated tests once but the selectors broke every time I changed a screen, so I gave up. I’m thinking staged rollouts and crash/funnel alerts but I don’t know what people use for the device side.
What’s on your checklist and how do you cover the devices you don’t have?
One year of hard work, countless hours of learning, experimenting, debugging, rewriting, and improving has brought this project to this milestone.
When I started building this library, I wanted to explore how far we could push native PDF rendering in React Native using JSI and the New Architecture.
What started as a personal engineering challenge has now crossed 501K npm downloads.
A year of working on:
Nitro HybridObjects for native document operations.
Fabric-based PDF viewer.
PDFium on Android and PDFKit on iOS.
Native document management, rendering and editing.
Performance improvements and continuous maintenance.
There were plenty of challenges, frustrating bugs, architectural changes, and moments where things didn't work as expected. But I kept learning, building, and improving.
A huge thank you to every developer who installed the package, tested it, reported issues, shared feedback, or recommended it to others.
As an independent open-source developer, seeing this kind of adoption is incredibly motivating.
501K downloads. One year of hard work. And we're just getting started.
We renamed a field in a Go response struct last week. The json tag stayed the same so every backend test passed but the app had a persisted react query cache holding the old shape and was reading a field that no longer got updated. Users saw that stale data and both sides looked fine on their own and neither side owned the test that would’ve caught it.
Backend is Go with chi, sqlc and postgres. Testing there is very good httptest for handlers, testcontainers for the db, stripe mock for webhooks. Our detox tests mock the API at the network layer with hand written fixtures, which is the problem because the fixtures just say what we think the API returns. When the real response changed the fixtures didn’t, so green.
and nobody tests the actual chain. I’ve been looking at pact or generating an openapi spec from the Go side and validating the detox fixtures against it plus bumping a version in the cache key so old shapes get dropped but not sure that’s enough though.
Is this always the backend team’s problem? Right now it feels like it belongs to nobody and if you do run full flows against a real api, does that live in the same CI or a separate pipeline?
I've been adding physical iPhone support to ExecBro, an MCP server I maintain for debugging React Native apps with AI agents. It runs on pymobiledevice3, a great library, and without it this would have been much harder. I thought it would be simpler, but edge cases kept coming up. In case you're automating a real device yourself, here are the ones that cost me the most time:
- Remote taps only work from iOS 27. Below that, the phone itself refuses them.
- Taps need the Xcode 27 developer disk image. If Xcode 26 is open, it remounts its own older image within a second, and taps fail with "Failed to start service".
- A sleeping phone accepts a tap session, reports success and taps the lock screen. I now check the screenshot before tapping.
- In landscape, touch coordinates stay fixed to the upright panel, so they have to be rotated using the orientation the phone reports.
- With the default 0.02 s gap between keystrokes, the second character of the first word typed after an app launch got lost every time ("igor" became "Ior"). A 0.1 s gap fixed it.
- `xcrun devicectl device info apps` returned an empty list on an iOS 27 phone with three apps installed, so finding an app's process to terminate it had to go through pymobiledevice3 instead.
- When the phone locks, the app drops off Metro, and a normal reconnect gives up long before you unlock it.
The basics now work: over USB the agent can launch and close the app, tap, swipe, type, press keys and take screenshots, in the same coordinates as on the simulator.
ExecBro is free to use and its core is MIT-licensed: github. If you've hit other device quirks, I'd like to hear about them, and constructive criticism is welcome.