They mostly help with centralising UI concerns. I’d imagine your camera app has less of that type of code and more code related to the respective camera APIs, which those frameworks don’t help much with. So I’d say no.

Last time I did this with JS it really needed to be tested on many phones and operating systems. iPhone/Safari behaved very differently from Android/Firefox.

Seems like you might need one implementation per platform entry in your platform matrix.

It might also depend on what you use the camera for - obviously all platforms have very different APIs for their camera stuff since they can do so many different things - so a cross-platform code piece might only allow you to access the most common denominator of features - which might be fine - or it might not be, depending on what you want to do.