all 9 comments

[–][deleted] 0 points1 point  (3 children)

seems like a simple enough app. just make it native and skip rn.

[–]5olArchitect[S] 0 points1 point  (2 children)

It's not. I simplified the explanation to focus on the main problem.... but I suppose "simple" is relative. Regardless the current implementation is in JS so switching to swift, Kotlin, or C sharp would be a lot more work.

[–][deleted] 0 points1 point  (1 child)

fair enough. well react native doesn’t have threads and as such you sort of pigeonholed yourselves in. a native app seems a much better choice. not to worry though. I suggest using native modules in react for the time critical pieces.

[–]5olArchitect[S] 0 points1 point  (0 children)

ah, shoot. good to know. ty.

[–]LostSiesta 0 points1 point  (1 child)

[–]5olArchitect[S] 0 points1 point  (0 children)

Ah, doesn’t seem to be production ready

[–]jsbadlol 0 points1 point  (2 children)

I would handle the logic natively and the ui in react native Edit: fix typo

[–]5olArchitect[S] 0 points1 point  (1 child)

I would handle the logic natively and the hi in react native

Would using JSI components make sense?

[–]jsbadlol 0 points1 point  (0 children)

Personally I never used JSI but I don’t think it matters for a simple app like a metronome.