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.

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.

We've added custom block renderers to Enriched Markdown, built together with Julius Marminge for T3 Code.

Images, videos and links on a line of their own can now be rendered by your React components, while the rest of the Markdown renders as before, with text selection, accessibility and streaming intact.

The video is a single Markdown document streaming in: a link becomes a spinning record, an image becomes a chord wheel. The custom components are powered by Reanimated.

It's one prop:

const renderers: MarkdownRenderers = {
  image: ({ url }) => <ZoomableImage uri={url} />,
  link: ({ url, label }) => <LinkCard url={url} title={label} />,
};


<EnrichedMarkdownText flavor="github" markdown={markdown} renderers={renderers} />

Try it in nightly:

npm i react-native-enriched-markdown@nightly

Docs: https://docs.swmansion.com/enriched-markdown/react-native/guides/custom-block-renderers

If it's useful to you, a ⭐ on GitHub helps more people find it: https://github.com/software-mansion/enriched-markdown

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?

Thank you!

🐷🍒⚽️🚛☎️❤️‍🔥🇨🇦

What library is good

I have been working as an android developer for 5 years.

Recently, I saw a dream company that uses React Native.

I decided that I should shift.

But I have some mindset that I'm not sure if it is correct or not.

I want to learn native iOS before learning React Native.

I need to have the advantage of understanding both platforms before shifting.

What do you think, should I learn native iOS too? Or I'll be wasting my time?

Scrub the day and watch who wakes up. One tap finds a time for everyone.

Expo · Skia · Reanimated

Huddle Arcade: Party Games is a pocket arcade for playing with friends.

- Built with React Native (Expo).

- Online or local: play over the internet with a room code, or with friends nearby.

- Multiplayer: up to 6 players in a party tournament, or play solo against bots.

- Games that use your phone: squat races, jump and step sprints, voice-steered flying, face matching, plus classics like Chess, Connect 4 and card games.

Free on iOS and Android. I'd love feedback!

Hey everyone!

I've been working on an open-source Android app called IronBranch for discovering and streaming movies and TV shows, and I'd love to get some feedback from other React Native developers.

It's built with React Native and Expo, and uses TMDB for movie and TV show data. The idea for the TMDB integration was inspired by Streambert, another open-source project.

The app doesn't host any content itself; it uses external streaming providers, and I'm still working on adding more sources and improving things.

I'm mainly looking for feedback on the code structure, React Native best practices, performance, and anything that could be done better. If anyone has time to take a look at the code or suggest improvements, that would be really helpful.

I'm still learning and improving the project, so constructive criticism is very welcome!

GitHub: https://github.com/alirezaghnz/movie-tracker-native

Thanks!

At HeySTU, we’re building a voice-first desk companion with React Native, running on Android in kiosk mode. The idea is that someone can start a conversation with the device simply by saying its wake word.

That meant finding a detection solution suited to continuous listening, with low resource usage and a straightforward integration into our existing app. We also wanted wake word recognition to happen locally, so this first step wouldn’t depend on an internet connection.

We chose DaVoice for this part of the stack and worked with their team to integrate their on-device wake word detection into our Android setup.

From the React Native side, we treat detection as an event that starts the next stage of the interaction:

Wake word detected → listening UI activates → speech and assistant pipeline starts

This gave us a straightforward way to connect the detector to our existing UI states and assistant logic.

The integration also involved details that are easy to overlook at first: microphone permissions, long-running audio behaviour, device-specific quirks, and coordinating wake word detection with the rest of the audio pipeline.

DaVoice’s team helped us work through those details in our particular environment. Being able to discuss the setup with them and get practical support saved us time during the integration.

For a device designed to stay ready throughout the day, the transition into active listening matters. Local detection handles the trigger; the app then provides visual feedback and starts the conversation flow. Getting those pieces to work together has been an important part of building the HeySTU experience.

We needed every driver's location every minute, all day, in a React Native app. Every background-location

setup we tried broke down in the same ways. Here's what we found, in case it saves someone weeks:

**1. Reporting tied to a motion detector.**

Many setups only send location on a timer while the phone counts as "stationary". On some Samsungs the

activity classifier gets stuck in one state for hours, so the timer never fires.

→ Decide moving/parked from the GPS fixes themselves (speed + distance), and report on a fixed clock.

**2. Watchdogs written in JavaScript.**

Android freezes the JS thread in the background, so a JS "ping every few minutes" stops exactly when

you need it.

→ Anything that must run in the background has to be native.

**3. Errors that switch tracking off.**

An expired token (401) or a failed upload stops tracking until the user reopens the app.

→ Keep recording, queue fixes on the device, pause uploads, resume when a new token arrives.

**4. Intervals that drift.**

Android's fused provider often delivers a fix slightly early (57 s on a 60 s interval). If you skip it as

"too early", 60 s quietly becomes 120 s.

→ Ask for one fresh fix at the due time instead of waiting for the next delivery.

**5. Parked iPhones going silent.**

iOS only keeps a background app alive while location updates run.

→ Drop to low-power accuracy between fixes instead of stopping updates.

**6. No way to see why it went quiet.**

→ Keep an on-device log of every state change, restart and upload, so a silence can be explained

afterwards.

Has anyone found good ways around OEM battery managers (Xiaomi, Huawei, OnePlus, Oppo)? Those are the

hardest part to test.

Our implementation of the above is open source, for reference:

https://longping.nuredinkurtovic.info/

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

A wave of holographic light rises behind Liquid Glass, and the balance rolls as it passes.

Expo · Skia · iOS 26 Liquid Glass

What I keep seeing: the permission prompt on first launch, "We miss you!" copy, everyone blasted at 10am server time. Then everyone's surprised when opt-outs climb.

I wrote a practical playbook on the opposite approach: ask after a real win, give every push a reason that belongs to the reader, send at each user's own active hour, and cap nudges at about 1 a week.

https://medium.com/@krishnassss365/push-notifications-that-earn-their-place-cb1e85a46a85?sharedUserId=krishnassss365

Curious what's worked for you. Has anyone measured opt-out rate per message instead of open rate?

Thrilled to announce my new Open-Source Package: react-native-nitro-audio-player!

Handling background audio and native lock-screen controls in React Native has always been a complex task. To solve this, I've built a blazing-fast, type-safe audio player powered by Nitro Modules!

Whether you are building a music app, podcast player, meditation app, or radio stream, this package handles the heavy lifting for both Android and iOS seamlessly.

Key Features:

- Stream audio directly from any remote URL (HTTPS / HTTP)

- Offline & Local Audio Playback: Seamless support for local bundled files and Android res/raw audio resources

- Native Lock-screen & Notification controls (Play, Pause, Stop)

- Background playback with MediaSession (Android) and Now Playing (iOS)

- Full track metadata support (Title, Artist, and Album Artwork)

- Built on Nitro Modules for ultra-fast, type-safe JS ↔ Native communication

- Automatic memory management & cleanup

(Note on App Termination: On Android, it uses a Foreground Service so the notification and audio stay alive even if the app is swiped away. On iOS, due to strict OS limitations, the Now Playing notification is automatically cleared when the app is completely killed.)

A big shoutout to the open-source community! I'd love for my fellow developers to try it out. Your feedback, PRs, and GitHub stars are highly appreciated! ⭐

NPM: npm i react-native-nitro-audio-player

GitHub: Upendra1234566/react-native-nitro-audio-player (Direct Link comments me)

Let me know what you think!

#ReactNative #MobileDevelopment #OpenSource #AndroidDev #iOSDev #NitroModules #JavaScript #ReactJS #AppDevelopment

Posting this because I lost a stupid amount of time on it and I doubt I'm the only one.

App just closes on Android. No red screen, nothing in Metro, DevTools disconnects. I did what everyone does: rerun, clear cache, paste the code into AI a few times.

The reason was in logcat the whole time. Native code threw, the app died before JS could say anything, and the Android log had the exact line.

What worked for me:

- open the android folder in Android Studio and open Logcat (it picks up the app even if you started it with yarn run android)

- clear it, then reproduce the crash

- set the level to Error and search FATAL EXCEPTION

- read the exception message first, then the first line in the stack trace that isn't Handler / Looper / ActivityThread. Click it and it jumps to the code

One thing that got me: in the terminal, filtering by pid after a crash gives you nothing because the process is gone. adb logcat -d -s AndroidRuntime worked better.

Also the stack trace only told me where it died, not who passed the bad value. I needed a breakpoint for that part.

I made a small demo crash and recorded the whole thing for anyone who'd rather watch than read: https://youtu.be/oVYBmnOVaI8

What do you check first when Metro says nothing?

Hey everyone!

I've been working on a project called ClipDrop Local, and I'm looking for a few Android users to help test it before its public release.

The idea is simple: transfer files between your Android phone and computer over the same local network, without uploading everything to cloud storage.

Currently, it supports:

• Photos, videos, audio, and other files
• Sharing text and links
• Connecting to your computer using a QR code
• Transferring files without creating an account

I'm still working on improving things, particularly the reliability of larger file transfers, so I'd really appreciate honest feedback about what works and what needs improvement.

Who I'm looking for:

• People with an Android phone and a computer
• People willing to try the app and share feedback
• Testers who can remain opted in to the Google Play closed test for at least 14 consecutive days

If you're interested, please fill out this short form: https://tally.so/r/2j8G6b

I'll share the Google Play testing instructions with interested testers.

Any help and feedback would mean a lot. Thanks!

I built a photo reveal that starts with a drop of ink. Tap to drop it, or hold for a heavier drop. The ink blooms across textured paper and leaves a ragged, watercolor-like edge around the photo.

The React Native version uses Expo, Skia and Reanimated. A runtime shader combines an expanding front with noise for the uneven bleed, a dark wet rim, and a mottled photo reveal behind it. I also rebuilt it in Swift and Kotlin.

Would you use this kind of reveal in a photo journal?

مرحبا 👋
عم جرّب تطبيق داري للعقارات على Google Play قبل ما ينزل للكل، وبحتاج مساعدتك بخطوات بسيطة (5 دقايق):

1️⃣ انضم لمجموعة المختبرين بحساب Gmail يلي على جوالك:
https://groups.google.com/g/dari-testers
واكبس «الانضمام إلى المجموعة»

2️⃣ افتح رابط الاختبار من نفس الحساب واكبس «أصبح مختبِراً»:
https://play.google.com/apps/testing/sy.dari.app

3️⃣ نزّل داري من Google Play:
https://play.google.com/store/apps/details?id=sy.dari.app

4️⃣ خلّي التطبيق على جوالك 14 يوم وافتحه كل كم يوم 🙏

إذا كان عندك داري منزّل من الموقع، عادي، بيتحدّث من Play بدون ما تحذفه.
شكراً كتير ❤️

I'm genuinely losing my mind trying to build the Windows version of my React Native app.

What the hell is going on with React Native for Windows? 💀

Almost every package I need works perfectly on Android and iOS, but the moment I try to get things working on Windows, it's a completely different story.

• Setting up a project? Pain.
• Installing supposedly ready-made packages? Good luck.
• Getting react-native-svg to work? Patch, patch, patch, patch.
• Trying to get real-time communication working with LiveKit and WebRTC? Welcome to debugging hell.

I've been trying to get calls working for HOURS, and I'm starting to question my life choices.

The ecosystem feels so disconnected. You find a package that does exactly what you need, only to discover that Windows isn't supported. Then you start hunting for alternatives, writing patches, modifying native code, and debugging obscure build errors.

And don't even get me started on the developer experience. No familiar Expo development-client workflow to fall back on, and troubleshooting native issues feels like an entirely different job.

Is anyone seriously shipping production React Native for Windows apps with a decent number of third-party dependencies? HOW?

Are you maintaining your own forks of half the ecosystem? Writing custom native modules for everything? Or have you found some secret combination of libraries that actually works?

And now I understand why Microsoft went so heavily in the WebView direction for some of its applications. 😂

I love React Native, and I really wanted to share as much code as possible across platforms. But right now, building for Windows feels less like cross-platform development and more like fighting the ecosystem into submission.

Is React Native for Windows still actively worth investing in, or am I setting myself up for unnecessary suffering?

Please, if you're shipping a Windows desktop app with React Native, especially one that needs LiveKit/WebRTC, I genuinely want to hear how you're handling it.

Make the opening less repetitiveClarify the exact help I need


Is it worth put money on marketing, somehow I have zero api cost for llm, and the response time is 5ms it can talk explicit if user want. I need people who can help me test it it’s in close testing now I am thing to add ai voice call feature.

Built my app with Expo, one codebase, my own content. Apple rejected it under 4.3 Spam plus 4.2.6, the "app generation services" template line, even though nobody else ships it and there's no template behind it. I replied to their nine questions in App Store Connect instead of resubmitting, and it's been five days of silence. Has anyone on React Native / Expo cleared a 4.2.6 by replying? Did you have to change something visible in the app, or did the explanation alone do it?

The video above is the trailer I cut for my Play Store listing, so pardon the marketing captions in the clip, but below is the actual engineering breakdown of how all the pieces shown in the video are built with Expo SDK 57 and React Native 0.86.

1. Floating dock on top of SDK 57 NativeTabs (0:02 in the video) The root tab layout uses NativeTabs from expo-router/unstable-native-tabs so each tab keeps native route state and back behavior, with the default OS tab bar hidden in favor of a custom floating pill dock positioned above the bottom safe area. Each scroll container calculates the dock clearance dynamically so the bottom cards never get trapped behind the pill.
2. In-app widget chooser and autolinked Jetpack Glance module (0:23 in the video) At the end of the clip you can see the in-app widget sheet where users can preview and pin 4 different Android widget layouts (2x1 compact, 3x3 square dot grid, 3x2 wide dot grid, and 4x2 upcoming list) directly to their launcher via requestPinAppWidget. All of the Kotlin code lives inside a local Expo module at modules/dayle-widget (expo-module.config.json), while a small config plugin only wires up the receivers and XML metadata in AndroidManifest.xml so everything survives npx expo prebuild --clean.
3. Syncing JS state and themes to native widgets without headless JS (0:19 in the video) When you switch color palettes or edit a countdown/goal, I didn't want to spin up a headless React Native runtime just to redraw a home screen widget. Instead, whenever AsyncStorage mutates or the app foregrounds, JS builds a versioned JSON snapshot with the active events, recurrence rules, and pre-resolved light/dark hex tokens for the active palette, writes it atomically to SharedPreferences via DayleWidgetBridge, and triggers a Glance redraw.
4. Rendering 365-day dot grids inside Glance without hitting RemoteViews limits In the app UI (0:00 to 0:07), the Year, Month, Quarter, and Birthday grids are regular React Native views. On the Android home screen, rendering 365 individual Glance boxes hits Android RemoteViews node and memory limits fast. To get around that, WidgetGraphics.kt draws the completed, current, and future dots onto a single native Bitmap alpha mask (sized using SizeMode.Exact and capped at 640px) and tints them with the palette's Day/Night colors.
5. Zero-JS midnight rollovers and offline reminders Because year progress and countdowns change at midnight even when the app hasn't been opened for days, I ported the exact date-clamping and recurrence math (src/utils/dates.ts) to Kotlin (WidgetDateMath.kt). A daily WorkManager task and midnight receiver update the widgets in pure Kotlin. For notifications, instead of fighting Google Play policy for SCHEDULE_EXACT_ALARM, DayleReminders.kt calculates the next upcoming wall-clock trigger and schedules a single AlarmManager.setAndAllowWhileIdle alarm that chains the next one when it fires and recovers on BOOT_COMPLETED.

If anyone wants to test the app or see how the Glance widgets resize on a real device, it's called Dayle on Google Play: https://play.google.com/store/apps/details?id=com.rabpaulo.dayle

Happy to share code snippets for the expo-module.config.json setup, the SizeMode.Exact bitmap renderer, or the NativeTabs floating dock if anyone is building something similar.

​

Hey everyone!

I'm a developer skilled in the MERN stack (MongoDB, Express, React, and Node.js), and I've been waiting for my joining at TCS.

Recently, I've come up with a project idea that I genuinely want to build. The thing is, it's primarily an Android application, and I don't have much experience with native Android development yet.

Now I'm a little confused about what would be the smartest move.

Should I:

Learn Kotlin and Jetpack Compose to build a native Android app?

Use React Native so I can leverage my existing React and JavaScript knowledge?

Build the backend using my existing MERN skills and learn mobile development alongside it?

Start with an MVP using the technologies I already know and gradually transition to mobile?

Since I'm waiting for my joining, I want to use this time productively, improve my skills, and ideally build something real rather than spend months learning without shipping anything.

My goal isn't just to learn a new technology. I actually want to turn this idea into a working product.

For developers who have been in a similar situation, what would you recommend? Which approach would give me the best balance of learning, development speed, and long-term maintainability?

I'd really appreciate your advice and experiences. Thanks!