react-native-nw-react-calculator

Thanks :) I am using ionic for the app. I wanted to test this framework while doing a real app. For the back-end, the API is build with express on AWS and I store my data in mongoDB on Compose.io So far, I can say that ionic was great to use. I did this project in May of last year even though I didn't push it in the App Store before October. In the meantime I did other App projects with react-native https://github.com/benoitvallon/react-native-nw-react-calcul... and I can say now that I would definitely go with react-native if I had to do it again. About ionic, I had a few difficulties with performance at the beginning, the app wasn't really smooth but it turned out to be more the Mapbox map that I used as a background than ionic itself. And after rethinking a few parts of the app, the experience for the user was nice.

Way cool! Looks like a common `Keyboard.js` will render either `KeyboardRender.js` on web/desktop or `KeyboardRender.ios.js` on mobile. KeyboardRender.ios.js: https://github.com/benoitvallon/react-native-nw-react-calcul... KeyboardRender.js: https://github.com/benoitvallon/react-native-nw-react-calcul... I'm wondering, though, if we can take this a step further and write Keyboard as the exact same code by composing it with more general components like `<View>` instead of `<div>`. This will require inline styles instead of class names, though. I theorize that this will be made a little easier for you with the use of react-native-web: https://github.com/necolas/react-native-web Cool project, though, thanks for sharing. Code is very clean, I'll definitely be using it as a reference.

I don't know much about React. When poking through the code I found this: https://github.com/benoitvallon/react-native-nw-react-calcul... Lots of ad-hoc global variables like _lastPressedWasEqual. Is this idiomatic?