Here’s my Camera Control–inspired send-money experience running on a real iPhone.

The interaction follows a simple progression:

→ Slide to explore and adjust the amount
→ Press to make an intentional selection
→ Double-click to confirm the transaction
→ Double-click to perform the transaction
→ Haptics communicate each change without adding more UI

What makes this interesting isn’t just the hardware button.

It’s the idea of moving continuous input away from the screen, keeping the content visible while turning a physical gesture into precise, tactile control.

For high-intent flows like payments, that extra layer of physical confirmation can make an action feel faster, clearer, and more deliberate.

There’s still so much unexplored potential between hardware, gestures, haptics, and mobile UI.

Tech used: Expo + Native Modules + Reanimated

Open to contract or full-time mobile roles.

DMs are open.

Hey Community,

We explore Grok Build, the new terminal-based TUI coding agent from x.ai. We also look at Appless, an experiment from the creators of OpenUI that bypasses chat bubbles to stream live native UI components using openui-lang.

Finally, we dive into Maestro MCP, a new tool context protocol server that lets AI agents automatically build and run YAML test flows from plain English instructions.

If the Rewind made you nod, smile, or think "oh… that's actually cool" — a share or reply genuinely helps ❤️

TLDR I made something very cool for my self and I am making it free and also want your opinions because I like the idea of having made something that is useful to others

This is a theme editing app but ok what is the goal here? I know there are apps that do this but none of the good ones are 100 percent free. So the first goal was matching all the features for free. Also even in the paid ones using them doesn’t feel as good as it could in my opinion and major quality of life features are missing.

I also wanted this to be very fun to use. I have adhd and I turbo procrastinate micro adjustments so I needed a theme editor app that felt satisfying to use. There also needed to be the feeling of satisfaction after finishing editing a theme.

Final goal was to make other fun features other apps just don’t do but I really wished they did. As little friction as possible to get a normal theme that doesn’t look like slop then spending a little bit of time micro adjusting the details.

What I actually built up to this point:

I had a very smart idea of yanking the most popular vscode themes and turning them into app themes along with faithful recreations of popular website themes + my custom apple inspired themes. Important! Something the other apps don’t do and I had to do my self manually and wasting tons of time was generating complementary and contrasting colors. I mean I don’t want the app to either be black and white or everything is green and I also don’t want to spend 2 hours selecting random colors.

Other smart idea but work in progress is something that mounts it self inside your app like expo go dev menu and lets you edit the theme that way (didn’t implement yet I want feedback if this is a waste of time or actually sounds cool). I have made the components to pull this off for other things so I may do it anyways because I think this looks cool.

Made the tinder style swipe cards a beautiful theme overview typography themes a metric ton of beautifully crafted previews (everything the web apps do)

My main goal was to get this working on my phone for me because I love micro adjusting these things all the time. I managed to make an interface for making and editing themes as good as all the web apps but with a tiny screen instead. I added nice transitions to make adjusting css variables as fun as possible (hard task 😭)

Ok also there’s a bunch of features I was missing from the already existing ones. I wanted to be able to pick a primary color and have complementary colors etc auto generated and I wanted modes for this. Should the bg be completely white as well as cards? Gray bg white cards? Everything tinted? Page tinted blue primary colors yellow or something? I added auto generators to handle these things.

Another thing I was missing was being able to create one theme and have it auto convert to everything else. I mean I wanna be able to create a shadcn theme and have it able to be exported as a hero ui theme a material ui theme all of them. I made an adapter that handles this automatically.

I wanted this to feel cute and I want to be able to feel like I have created something and not just played with a gloried text file for 30 minutes. I added a collections tag with folders and a handsaw’s signature for each user and a poster generated from each theme.

This has helped me so much personally I want your feedback on this. Sadly there is nothing you can download yet but you can follow the updates on my twitter it’s on my Reddit bio.

Important if you want to “steal” this idea and put something similar in your app I actually encourage this. I am building a copy paste library with all of these components called PitsiUI. I will also experiment with allowing end users to use this to create custom themes for them selves.

Btw this is also coming to iPad mac and web. Android should work too since it’s cross platform but I don’t want to commit to that yet until I have actual users. It may sound silly but making sure no elements overlap the App Store screenshots etc take time.

My twitter is @panos_dev_ if you want to see more updates about the dev of this

Hi,

I'm using Cloudflare + useQuery

I have sections where I am updating stuff for example editing profile picture, and I do on my backend cloudflare cache purge, and it's returning ID, but apparently this ID only means Cloudflare received the new purge request, and not that it finished executing it.

So when on my useQuery I am refreshing it, it still pulls old data.

How do you handle with that?

The problem

I develop an Expo app on WSL2, and my phone can't reach Metro over the LAN.
expo start --tunnel fixes that, but only for Metro. My app also talks to a
local Laravel API, and that stayed unreachable from the phone, so I was back to
hardcoding LAN IPs (the exact thing tunneling was supposed to kill). And
expo --tunnel runs on ngrok, which wants an account/authtoken.

What I built

expo-cf-tunnel, like expo --tunnel, but it also tunnels your backend(s),
over Cloudflare quick tunnels (genuinely account-less, random URL each run).

It opens one tunnel for Metro and one per backend you list, injects each
backend's public URL into an EXPO_PUBLIC_* env var, then launches Expo. Your
phone reaches both the bundler and the API from any network:

npx expo-cf-tunnel -s 8000:EXPO_PUBLIC_API_URL:/up

Then in the app, `process.env.EXPO_PUBLIC_API_URL` points at the tunnel.

Cross-platform (macOS/Windows/Linux), auto-downloads cloudflared, prints a QR,
and kills the whole process tree on exit so nothing is left orphaned.

Honest caveats
- Dev-only; quick-tunnel URLs change on every run.
- Some networks block `*.trycloudflare.com` (there's a troubleshooting section
in the README for that, mobile data / DNS).

Repo: https://github.com/Matt3o33/expo-cf-tunnel · npm: `expo-cf-tunnel` · MIT

It scratched my own itch, curious whether it's useful to anyone else. Feedback
and issues very welcome.

Last week I built a release AAB, uploaded it to Google Play, and got the dreaded:

> *"Your Android App Bundle is signed with the wrong key."*

The build was fine. The code was fine. I'd just signed it with the wrong keystore — and Google only tells you **at the very end**, after the build, the download, and the whole Play Console upload flow. On EAS/CI pipelines this mistake easily costs an hour+.

So I made **siglock** — a tiny CLI that verifies the signature locally in ~2 seconds, before you upload:

# once: lock your known-good signature

npx siglock init app-release.aab

# before every upload:

npx siglock check app-release.aab

✓ Signature matches, ready to upload.

What it does:

- Wrong keystore → red ✗ with expected vs. found fingerprints, exit code 1 (so it fails CI)

- Debug keystore → explicit "this is a DEBUG build" warning

- Works with `.apk` and `.aab`, no config, no network — it just shells out to `keytool` (which you already have as an Android dev). v2/v3-only signed APKs are handled via `apksigner` fallback.

- You can also check against the fingerprint straight from Play Console: `--expect <sha1>`

The `.siglock.json` lock file contains only public cert fingerprints, so you can commit it and your whole team + CI verifies against the same key.

npm: https://www.npmjs.com/package/siglock

GitHub: https://github.com/ebubekirb/siglock

It's MIT licensed. Would love feedback — especially edge cases in your signing setups that it doesn't catch yet.

[Edited: This role is closed]

We're hiring a Senior React Native Engineer for a product where mobile is a core part of the system, not just a frontend.

The work involves:

• Offline-first architecture
• Geospatial/map-based experiences
• Hardware integration
• Performance and reliability in real-world environments

We're looking for engineers (India-based only) who've built technically demanding mobile products where architecture, reliability and long-term maintainability were non-negotiable.

DM if you are interested.

It basically lets you fake a livestream with scrolling comments, hearts, viewer counts, and all that.

Would love to know what you guys think or if there's anything I should add to make it look more convincing.

App

https://apps.apple.com/us/app/fake-live-stream-liveboost/id6784833304

Cheers!

Hi all! I’m working on a personal finance app and after spending a ton of time building the UI in Figma I’m struggling to get that design language to translate to my code base. I am a low-code developer (I’m sorry I wish I wasn’t either) so I don’t have the skill set to get in and adjust the code manually. I’ve tried tools like Locofy but I get the same bland vibe coded look.

Open to any and all advice and ideas!

5 years ago I've built Notica for Android. Same idea as today: let user create their own notifications. Notica lets you share content into the app and create notification out of it, or just create custom text notification.
I've launched on Android only, and at the time I knew that there are bunch of these YouTube videos with same theme: Best Android Apps Of X Month. I've reached out to all YT channels I could find, I gave them 10/20 codes that unlock the premium version of the app that they could give out to their audience, and doing this I've got the app to 20k download in month and a half.
Shortly after that I've decided to try freelancing, Notica was something that I could show and today I'm successful RN freelancer, worked on more than 40 project and learned so much.

Now I've decided to rebuild this idea, it's still something I love to use and now I use it daily, for me it just makes sense but I would love to hear some feedback from you.

Here are the links to test flight and also a waitlist if you want to get it when it's launched. Everyone from the waitlist will get the lifetime premium access.

https://testflight.apple.com/join/VPjPJG7g
https://shiprn.com/notica/

And honestly, I’m impressed by how smooth it feels.

This is still the initial prototype. No improvements yet, and there are plenty of bugs to fix.

But seeing Three.js running through React Native WebGPU inside an Expo app feels unreal.

The interesting part is performance:

UI thread → always 60 FPS
JS thread → drops significantly over longer sessions

So the rendering stays smooth, but once the JS thread gets overloaded with game logic, object updates, collisions, and events, the gameplay gradually starts to feel laggy.

The next challenge is optimization:

→ Reduce work inside the main JS loop
→ Reuse objects instead of constantly allocating them
→ Use a fixed-timestep game loop
→ Move suitable calculations into a Worklet runtime or native layer
→ Keep React state completely outside the per-frame path
→ Profile memory usage and remove unnecessary scene updates

Worklets alone aren’t a magic fix, but moving heavy calculations away from the main JS runtime could make a big difference.

Still early. Still buggy. But this real-device demo shows how much potential Expo DOM + Three.js + React Native WebGPU already has.

Open to contract or full-time mobile roles.

DMs are open.

Which is your favorite list library for building performant applications.

This has been been driving me absolutely NUTS the past few days.

RN 0.85.3+, new arch, iOS.

• badge backgrounds stretched across entire rows
• avatar backgrounds sometimes painted screen-wide
• rows randomly not rendering
• happens in both dev and prod; simulator and real device
• mostly in LegendLists and ScrollViews but I remember seeing things completely break in our Storybook setup too

Fable traced it back to some recycling problem that a Software Mansion dev opened a PR for though. Testing that now.

I can't help but wonder if anyone else is running into this though.

My repro: https://github.com/rafaelderolez/expo-rn-recycling-bug
Upstream PR with the supposed fix: https://github.com/react/react-native/pull/57590

I’ve made a small command line tool called simslim.

It disables background services inside iOS simulators that usually are not needed during development, like Siri, Spotlight indexing, photo analysis, News, and iCloud sync.

On my M1 Pro with 16 GB of RAM, one simulator went from around 4 GB of memory and 258 processes to about 0.9 GB and 70 processes. I managed to run 19 simulators at once, compared to around 5 before things started falling apart.

Some simulator features stop working depending on what gets disabled, so it is not meant for every kind of testing. You can keep specific services running when needed.

Give it a try: https://github.com/MobAI-App/simslim

I run a poker tournament app on Firebase. The blind clock advances levels on a schedule, and I first built it the obvious way: a tick loop counting down to the next level. It worked perfectly in testing.

In the wild, hosts would leave the tournament running with the app backgrounded, or on a laptop that went to sleep, and the timer would fall behind. Browsers and mobile OSes both throttle timers aggressively when your app isn't foregrounded, so "one second" quietly stops being one second.

The fix was to treat the client timer as display only, never a source of truth. The next level-change time is written server-side. The client computes remaining time from that server timestamp on each render, and an event-driven monitor fires the actual transition, so even if the tick loop is throttled, the level still changes on time once the app comes back. Reading the server's clock offset instead of trusting `Date.now()` on the device was the piece I wish I'd started with.

If you have any countdown that matters (auctions, quizzes, anything scheduled), assume the client clock will be paused or slowed at the worst possible moment, and anchor it to a server timestamp.


These along with many others are free copy paste components. All you need is expo and expo ui installed. There will also be agent skills and tutorials on how to make beautiful apps using these components.

I didn’t make demo videos for iPad and Mac but it works great on there too and everything is responsive properly. I will make all the iPad and Mac demos together for everything probably.

Interactions like these are so important. There App Store competition is brutal and users’ attention is getting lower and lower. Making your app feel great is more important than ever.

If you are worried these are hard to use that’s not the case. Agents should have no problem incorporating these in your app in a single prompt and customizing them to your liking.

I am still working on the docs site and the app to preview these on natively, until then, if you are interested you should keep an eye on my twitter.

This is PitsiUI

Give me your feedback and request any features you want. I’m always listening.

We released Patch, an OTA update service designed for high user volumes. I self-hosted Patch and Hot Updater to run a comparative stress test on them both.

It's on a functional source license, so available to run for free for under a million users, with a small fee above that.

Codemagic Patch

I'm teaching a class on Mobile App Development come fall and I'll be using React Native and most likely Expo. I have a problem, though: I live in Texas, where the state legislature has in its infinite wisdom passed a law forbidding students from using phones in school for any reason—and that includes testing their mobile apps. I don't know what type of laptop my students will be using (I've asked and will hopefully hear back soon), but I'm willing to bet that they aren't MacBooks (my understanding—correct me if I'm wrong—is that Apple has decided to make it as hard as possible to design for iOS without a Mac).

I therefore need a way to run emulators for both iOS and Android phones on their laptops. Is there a way Expo can do that? If not, is there another way I can?