misha67's comments

I'm in the same boat. Planning to go iOS first, since I'm an iOS developer and don't know Android. Go with what you are most comfortable developing.

React Native might also be a good choice. I was pretty impressed with what it could do on iOS, but I had challenges getting it to work on Android.

The threat of having to write unit tests will not have nearly the effect of actually writing them.

It's too easy to fool yourself into thinking you've written testable code.

Done well, unit tests are invaluable. I'm a relative late-comer to unit testing, but can attest to its value.

The discipline of unit testing forces me to think about what risks I'm introducing with my new code.

Unit tests drive better design - smaller classes, looser coupling, better separation of concerns, functions that don't have side effects.

Best of all, unit tests reduce regressions. I can't count the times my test suite has prevented me from introducing a bug in my app.

I can refactor code with much more confidence than if I did not have 400 unit tests checking my work.

Most recently, these tests proved their worth when upgrading my app to Swift 3.0.

> Which kneecap do you want the bullet in?

Funniest thing I've heard all day!

Honesty.

Well said. "Monolith" is a pejorative that prejudices any discussion of said code.