I built some minimal interaction and animation using Skia and reanimated.

🔗 GitHub: https://github.com/rit3zh/interactions

I am an app developer working from the past 2 years. I have a job but i want to make money on the side. I was hoping to have a passive income from maybe an app. But i don’t know how and i don’t know where to start. What are the kind of apps that make money? And how do i go about doing it even if it takes a lot of tries at least i would have published apps on app store and/or play-store.

It prints; you drag; the totals roll. Settle tears it off.

Expo · Reanimated · Gesture Handler

Most RN errors aren't hard once you know which layer broke. This is the routine that saves me the most time:

1. Read the first error, not the last line. Red screens and build logs usually end with something generic. Scroll up to the first real error and the top stack frames that point into your own files.

2. Name the layer. Metro couldn't bundle (Unable to resolve module), JS crashed at runtime (Text strings must be rendered within a <Text>), a native module is missing (works in a dev build, crashes in Expo Go), or Xcode/Gradle failed to compile. Each has different fixes.

3. Check how you run the app. Expo Go only has the native code bundled into it. If a library ships its own native code, you need a development build, and if you added it after building, you need to rebuild.

4. Clear caches before anything deeper. npx expo start --clear fixes a surprising number of resolution errors after moving files or changing Babel config.

5. Align versions. npx expo-doctor and npx expo install --fix. SDK/library mismatches are behind a lot of both runtime crashes and EAS build failures.

Two sneaky ones worth knowing:

• {count && <Badge />} renders 0 as raw text when count is 0, which gives you the "Text strings must be rendered within <Text>" error. Use {count > 0 && ...}.
• localhost on a phone is the phone. Use your machine's LAN IP for a local API.

What's the error that cost you the most time?

Hello,

I have a website that I would like to also have it has an app on android and Apple. The catch is I need the app to work offline and have documents downloaded offline, modifications to be made, saved and shipped once back online.

Claude was suggesting to have the website in the app but it won’t perform properly I think.

But I think it’s better to have a native app since there is all the offline accessibility features that need to be integrated. I am trying to create a full native app but it’s pretty much ai copying the whole website. Also I would like to have to modify all from one location.

(Code is currently python, xml, JavaScript, html/ces, SQL for database)

Is this feasible and what should I look out for? Should I look in to flutter instead?

EDIT: It is pretty much an ERP system and the features needed offline are: checklists, time punches, plans and documents. For all of them we also need to be able to edit and resubmit offline, where it saves on the phone and pushes it once back online.

Thank you!

We needed every driver's location every minute, all day. Here's what kept breaking and what fixed it:

1. The motion detector gets stuck (some Samsungs), so nothing is reported for hours.

Fix: report on a fixed clock, and work out moving/parked from the GPS fixes.

2. JS timers stop in the background.

Fix: do it in native code.

3. An expired token (401) stops tracking.

Fix: keep recording, queue fixes on the phone, upload later.

4. Android delivers fixes early, so 60 s quietly becomes 120 s.

Fix: request a fresh fix when the next one is due.

5. Parked iPhones get suspended.

Fix: keep location updates on, at low accuracy between fixes.

6. No way to tell why it went quiet.

Fix: keep an on-device log.

Has anyone found a good way around Xiaomi/Huawei/Oppo battery managers?

We open-sourced it as Long Ping (free, MIT):

https://longping.dev

https://github.com/nuredin-kurtovic/long-ping-background-location-plugin


I'm researching an Expo starter kit for developers who want to build subscription-based mobile apps.

I'm particularly interested in the setup around authentication, Firebase, RevenueCat and store builds. Before building the kit, I want to understand where people actually get stuck.

If you've built an Expo app recently:

- What part of the initial setup took longer than expected?

- Did you start from scratch or use a starter kit?

- What would make a starter kit worth paying for?

I'm at the research stage and would appreciate honest answers, including if you think a paid starter isn't useful.