Apple Voice Memo Widget

🫰

Wireless debugging is great until you actually use it day to day. Three things kept costing me time:

1. The connect port changes every time you toggle the setting.

2. The pairing port is different, single-use, and dies when you close the dialog.

3. A phone on the wrong subnet fails identically to a real protocol error, so you can't tell a network problem from a broken adb.

So I built adb-nearby.

npx adb-nearby scans your network. If there's one device, it connects — that's the whole interaction. If there are several, it lists them and you pick.

adbn pair prints a QR code — scan it with the pairing dialog and you're done. No typing codes, no chasing ports.

MIT, no telemetry.

https://github.com/JassiSingh08/adb-nearby

[ Removed by Reddit on account of violating the content policy. ]

fair warning, creating mobile testing/developing tool so im biased. not pitching anything, genuinely curious about is the day to day loop of devs and what tools everyone is using. also how is getting a build in front of someone who isnt a dev is solved. designer, pm, client. testflight every time after few changes?

what im curious about is whether people have landed somewhere different. is everyone just renting macs buying real devices? and is expo go covering more than i think it is?

I wanna create an expo development build for my app on my physical iphone device and i am on windows, I heard about that it requires apple dev account, please tell me it’s not true

I built RoomWise AI using React, a simple way to see what a room could become before buying furniture, repainting walls, or committing to a layout change.

You add a photo of your space from your camera or gallery, choose what you want to change, and explore different directions from there.

Free to use with limited. Pro Priced at $3.99 for Weekly and $39.99 for Yearly.

Still early, but I’d genuinely love to hear some feedback from people willing to give it a try! Harsh criticism welcomed.

(P.S. Designed the screenshots myself with Canva).

It's an agent skill + CLI built on top of Argent by SWM. I called it Goldie. It's completely free and open-source on GitHub.

You simply ask your favorite coding harness to make you App Store screenshots and Goldie will built your app in release mode, control it using Argent, take screenshots and wrap it into marketing store screenshots.

It also comes with a "Studio" allowing you to tweak the designs by hand.

I started building it for App Store iOS screenshots only but it also works with Android mobile apps too. iPads are coming in the next version.

It works well with React Native apps but it also works with SwiftUI, Jetpack Compose, Flutter etc

To get started run in your project:

npx skills add kacperkapusciak/goldie

PS: If you've seen some posts on X on this, that's me!

Just vibe coded a Video Compression app, the videos I take from my phone cam were damn ridiculously large so I decided to start this project

Compressed video from 90MB to 17MB

90mb for a 1minute video is fkn insane💀

Built with ReactNative and expo

I shipped AlloGames a few days ago, built with Expo and React Native. It’s a social app for video game collections: you file the games you own, rate them, review them, and talk to other players.
It got bigger than I planned, 60+ screens, covering:
• Collection: playing, finished, dropped, want to play, with ratings
• Showcase: pin four favourites to the top of your profile
• Marketplace: buy and sell games with other players, sorted by distance location
• Payments: a subscription that removes the ads, through RevenueCat
• Plus a daily quiz, tournaments, chat rooms, and library import from Steam, PlayStation and Xbox
Stack: Expo SDK 57, React Native 0.86, expo-router, Supabase (Postgres + RLS + edge functions), RevenueCat, AdMob.
If you’re building something similar, ask me anything.
Happy to share what worked and what cost me the most time.
App Store: https://apps.apple.com/app/id6799963120
Google Play: https://play.google.com/store/apps/details?id=com.prismago.allogames

I’m trying to understand a couple of pain points QA teams deal with regularly:

• How do you figure out what needs to be tested after a code change?
• When a test fails, how easy is it to tell whether it’s a real bug, flaky test, or locator issue or test data issue, or environment issue?

I’m exploring whether these are actually big enough problems to solve, so I put together a very short survey.

Would really appreciate any responses or even thoughts in the comments. [1min max, just clicks]

Lik: https://forms.gle/1EyP5Bz3CNBB2DrM7

Thanks!

Or does it still make the app look cheap / unprofessional?

Hi everyone!
Since quite a while I am looking forward to implement shared element transitions in my app. I was super happy when I found out that the team from react native reanimated was working on bringing it to the new arch at the end of last year. However, since then it is behind a feature flag and not recommended to use in production apps. And I also could not find any roadmap or similar for it.

Are you using shared element transitions in react native? If yes, how? Do you know if they will be production ready, soon?

You'll no longer need a real device to test anything camera related!

Buoy Desktop now fabricates a camera for it. Pick a source on your Mac and every booted simulator sees a real camera:

Options -

• Your Mac's webcam

• An image or a video file

• A generated QR or barcode

• A live region of your screen, drag a rectangle, the camera follows it

• A test pattern

No SDK, no pod, no change to the app you're testing. It's entirely host-side, so it works with the build you already have.

A dialog whose body is a well to write in. The recess is the affordance it says "this is where you type" before a word has been read.

One decision worth explaining: Submit hands the message back without closing the dialog. A dialog that closed on the press would take its own error message with it and the message the user just wrote.

The footer is a slot, so it handles multi-step flows: score first then words, tags over the field, a confirmation after sending. The shell holds still while the well changes, so the dialog reads as one object answering rather than a second one arriving.

Part of PanelUI, an open-source component library for Expo. Copy-paste or CLI, you own the source.

https://github.com/panel-ui/PanelUI

Been building DriveTrack, an automatic trip logger that detects when you start/stop driving and records your routes in the background, in React Native. Wanted to share a rabbit hole I went down that other RN devs building background/location apps might hit.

What I actually wanted from the start was reliable, deterministic start/stop points — so I went with Bluetooth connection events as the trigger (connect to your car's Bluetooth = trip start, disconnect = trip end). On Android this was straightforward: wrote a native module that listens for BT connection/disconnection events in the background. Rock solid, and better battery life than anything sensor-based.

iOS doesn't give you an equivalent background hook for Bluetooth state changes, so that approach was a dead end there. I tried falling back to motion detection (driving vs. stationary) instead, but background motion-based triggers get heavily throttled/killed by iOS, and I couldn't get reliable start/stop detection out of it no matter how I tuned it.

Ended up relying on Apple Shortcuts automations — "when connected to [car Bluetooth]" / "when disconnected" — to fire the trip start/stop instead of trying to detect any of it app-side. Not as seamless as I wanted (it means asking users to set up a Shortcut), but it's the same reliable trigger I originally wanted, just moved outside the app since iOS won't let me do it natively.

Trips get recorded via GPS and played back on an interactive map, with stats/history over time — all stored locally on-device. I also built a small web tool on the landing page that lets you open your local SQLite backup and view your trip history in the browser, in case anyone's curious how that's wired up too.

Happy to go deeper on the native module / Shortcuts setup if anyone's dealing with something similar.

Android: https://play.google.com/store/apps/details?id=io.github.frankoprifti.drivetrack
iOS: https://apps.apple.com/us/app/drivetrack-track-your-drives/id6796486326

It's a Cortex brain training games that scores your attention, focus , short term memory , long term memory , path memory and many more .

Game link : click here

Please review my game what should I improve.

It supports many features such as exporting AppStore screenshots for several languages at the same time.
AppStore Download: https://apps.apple.com/us/app/mockup-kit-store-screenshots/id6784220988?mt=12
Website: https://mockupkits.com/

Link for the source - https://newly.app/compare/native-hybrid-pwa-comparison

I always thought RN had leverage in terms of adoption due to it being open source.

Open ended question- At this point for mobile dev, is it better to switch to the "native app market" (kotlin/swift), or master flutter and RN and gain dominance over the "cross-platform app market" ? I am talking primarily in terms of money, and job availability

É permitido usar pix para vender assinatura de aplicativos apple e android? Se sim como funciona essa taxa da apple e android?

I'm tired of watching React Native apps get slow.

At the beginning everything ships fast and feels great. Then the app grows. More teams, more code, and one month at a time it gets a little less usable. And you know exactly what's coming.

The chaotic re-renders. The slow data management and persistence. The heavy animations. The slow polyfills. The time-sucking RN upgrades. You spend week after week fixing bugs and performance issues, and a month later a single line of poorly performing code ruins the app again. Even with all the guardrails in place, and the guardrails need maintenance too.

Even with all the new stuff, the New Architecture, JSI, TurboModules, Fabric, Hermes, and now the React Compiler. It helps, I'm not saying it doesn't. Still not enough. The numbers below are against all of it turned on.

I came to the conclusion that React Native is great for smaller apps but keeping it fast doesn't scale. (Yes, I know huge apps ship on RN. That's not the point. The point is what it takes to keep them fast.)

Then, kind of by accident, I ran into a chart library (react-native-graph) that draws with Skia and it's extremely fast. Skia seems to be growing in popularity with React Native, and it got me thinking: could Skia be the only rendering engine, instead of platform UI? Changing the whole rendering system would be way too much work though... wouldn't it?

That question led to another one: the JS engine. Is Hermes scalable? Can it handle heavier JS loads? I know it's optimized for mobile, but did it find the best balance of memory and speed? And on top of that, crypto and half the web platform are still polyfills.

And then React itself. Is it optimized enough for mobile, without us spending all that time fighting re-renders and a JS thread that keeps getting clogged?

So, I researched. (Read: I went down a rabbit hole.)

Turns out Flutter, which is considered to be fast and more scalable, already renders everything itself, through its own engine (Skia originally, Impeller now). Unless you embed a platform view, the OS is never asked for a widget. Not once.

Bun seemed to be the fastest JS runtime out there. It runs on JavaScriptCore, Safari's engine, which works without a JIT, and iOS apps can't JIT anyway. And it brings fetch, crypto, Buffer and TextEncoder built in. No polyfills.

Solid seemed to be one of the fastest JS frameworks, and when I found it, it looked like React if it were extremely optimized. Same JSX, same components, but components run once, and signals update only the nodes that changed. No virtual DOM. So could React be optimized like that?

Changing the rendering engine and the JS engine would be a crazy endeavour. The accessibility layer, the plugin ecosystem, the platform look and feel... I know. I did it anyway.

So I tested what happens if you bring those three together:

• Bun, which I cross-compiled to run on iOS and Android
• Solid as the JS framework
• Flutter for rendering

Solid runs inside the embedded Bun runtime and writes what to render into a shared memory region that Flutter reads every frame. No JSON and no platform channel in between. I named it Skal. Mixture of Solid + Skia, and it means cheers if you have ever seen a viking show 🍻.

Here are some highlights from testing on a Samsung Galaxy A14 5G (a budget phone), release builds on both sides:

That is what I was chasing. The app can get bigger without every interaction getting heavier. Fast on the first screen, still fast on the hundredth.

Repo: https://github.com/skal-multiplatform/skal

So, could React Native ever be optimized like this? Genuinely asking.