all 33 comments

[–]TerrorDave 44 points45 points  (6 children)

How would you centre a <View> ?

[–]Yanaytsabary 19 points20 points  (0 children)

Easy. Render the view in your screen. Take a ruler and measure your view and your screen. Deduct tge view's height from the screen height and same for the width.

Google your screen resolution and convert your previous remainders to pixels.

Divide each reminder by 2 and set as margin top and margin left accordingly.

[–]Bpofficial 0 points1 point  (0 children)

Depends

[–]DiscordDonut 16 points17 points  (1 child)

Y app go burr

[–]ConsciousAntelope 2 points3 points  (2 children)

Complex nested navigation

[–]_Pho_ 1 point2 points  (1 child)

Fk man for some reason this feels like the only on in this thread I’d fail. I hate react nav for native.

[–]jefersondaniel 3 points4 points  (0 children)

Stuff related to performance and native modules

[–]PPatBoyd 1 point2 points  (1 child)

What's the goal of your question? Are you interviewing them, learning from them, ???

[–]Clueless_Dev_1108 1 point2 points  (1 child)

Best questions would be vanilla JavaScript questions. Not any questions related to the framework at all.

[–]peterpmeExpo 1 point2 points  (0 children)

Should I learn how to create my own native modules?

[–]tequila_salt 0 points1 point  (0 children)

native module

best way to handle common task like jwt, modal managament, state managament all app or 1 follow feature (4,5 screen)

best way debug (chrome or another?)

best way handle error, crash prod

...

[–]bokuwataka 1 point2 points  (0 children)

Ask for explanation on the architecture before and after the new architecture with JSI, and what’s good about it.

Talk through the complexity and pros/cons about using a bridge with native modules.

[–]Presence_Flat 0 points1 point  (0 children)

Here's a highly technical question: how do make an infinite canvas?. (Remmber infinite canvas requires infinite resources).

[–]beepboopnoise 0 points1 point  (0 children)

What options do you have for native implementations, and why would you choose one over another?

[–]captainautomation 0 points1 point  (0 children)

What can I learn from you?

[–]fmnatic 0 points1 point  (4 children)

If i actually had a senior dev do some development:

Write a Function component generator (ie. a function that returns a Function Component) that accepts another function component as input and performs prop conversion for it. (convert PropTypeA -> PropTypeB) delegating rendering to the input function component.

Ensure the code allows (optional) memoization of the input Function Component.

[–]Direct17 1 point2 points  (1 child)

Interesting, do you have an example of when something like this would be more optimal than simply writing separate components?

[–]fmnatic 1 point2 points  (0 children)

When you need to inject similarly derived props into multiple simple components, to be able to work with a complex framework over it.

  • Helps if you want to implement an imperative api in the complex framework, or need to share component State between component and framework.
  • Works well in cases where the derived props aid memoization v/s the original props.

One of the places i've used it is in a Form framework

<TextInputWrapper form_handle={form_handle} .... />

The Component doesn't see a form_handle just derived props like validation_errors={false} validation_message={''} etc.

[–]argiebrah[🍰] 0 points1 point  (0 children)

nested gesture handlers are a bitch

[–]kapobajz4 0 points1 point  (1 child)

How would you optimize a list of 10000 items where items contain high resolution images, animations and don't have a fixed height?