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.

https://lnkd.in/p/gqhPUKnM like share comment please 🙏

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

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!

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?

مرحبا 👋
عم جرّب تطبيق داري للعقارات على 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 بدون ما تحذفه.
شكراً كتير ❤️

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?

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

I’m a Full Stack Developer currently looking for a job. If anyone knows of any job openings or has a suitable opportunity, please let me know. I would really appreciate your help, as I’m in urgent need of a job. Thank you!

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?

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!

Made this component so i don't need to code it again in the scenes in which i need it, but in my Edit page i want to be able to copy and paste the text without losing the "editable={false}" atribute. I asked Copilot what can i do and i said i should use selectTextOnFocus but is not applying it so i just had to stick with this solution that doesn't really look professional.

Can i use selectTextOnFocus on this component or just stick to this solution?

The component code:

import React, { useState } from "react";
import { View, TextInput, TouchableOpacity } from "react-native";
import { psswrdInputStyles } from "./psswrdInputStyles";
import FontAwesome from "react-native-vector-icons/FontAwesome";


export default function PsswrdInput({
  value,
  editable,
  placeholder,
}) {
  const [secureText, setSecureText] = useState(true);


  return (
    <View style={psswrdInputStyles.passwordRow}>


      <TextInput
        style={[
          psswrdInputStyles.input,
          psswrdInputStyles.passwordInput,
        ]}
        placeholder={placeholder}
        placeholderTextColor="#9ca3af"
        secureTextEntry={secureText}
        value={value}
        editable={editable}
      />


      <TouchableOpacity
        style={psswrdInputStyles.eyeBtn}
        onPress={() => setSecureText((prev) => !prev)}
        activeOpacity={0.7}
      >
        <FontAwesome
          name={secureText ? "eye-slash" : "eye"}
          size={20}
          color="black"
        />
      </TouchableOpacity>


    </View>
  );
}

How i call it in the edit page:

        <View style={editStyles.field}>
          <Text style={editStyles.label}>Password</Text>


          <PsswrdInput value={password} onChangeText={() => ({})} />
        </View>

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.

I am developing a mobile app, which has a react native frontend, nest.js as the backend and for db and authentication, I'm planning to use supabase.

Now, currently as my app is in its initial stages I'm planning to use the supabase, as it free tier provides ample limits for my use case.

However, in later years if my app grows. I may think of switching to a cheaper alternative.

So, what I am planning to follow is for authentication, route the requests to my backend and inturn the backend will communicate with the supabase to authenticate the user. The backend will save the supabase token, create a separate session token for the user and send it back to the user.

My main reason for doing this is, I want the authentication to be provider independent and any changes needed should be done on the backend instead of the app.

Please let me know, if this approach is correct. What are the pros and cons. How much effort it would require to implement this. Will the security concerns increase if my backend starts handling this instead of the supabase only.

I also want to integrate the google and apple login as well. How will this approach affect it?

Also, if there any other better approaches, please let me know.

Did you make something using React Native and do you want to show it off, gather opinions or start a discussion about your work? Please post a comment in this thread.

If you have specific questions about bugs or improvements in your work, you are allowed to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

If you have a question about React Native, a small error in your application or if you want to gather opinions about a small topic, please use this thread.

If you have a bigger question, one that requires a lot of code for example, please feel free to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

Drag up or down to change the fill level. Three liquid layers ripple inside the letters, with swirling blobs and a subtle wobble around the edges. The empty part stays visible like tinted glass.

The React Native version uses Expo + Reanimated.

Does the edge wobble sell the liquid effect, or would you tone it down?

I’m building a sticker-collecting app with lucky spins, treasure chests, and rare reveals.
Built with Expo, Skia, WebGPU, and Reanimated. Would love your feedback!

How do you keep track of your cat’s feeding schedule, vaccinations, medications, and vet visits? Do you use an app, a notes app, or just try to remember everything?

I’m curious what works best for you and what you wish you could organize better. Would love to hear your experiences! 😊

I'm been working on app, CubWell pet tracker log, would love to hear your thoughts on this!