onLayout Attribute (a bit)
The <KeyboardAvoidingView> is one component provided by react-native, which (magically) handles the screen to re-layout when the virtual keyboard opens on ones phone.
This component comes not without challenges, I had actually written about it and I still keep finding things, which make me dig deeper into it to understand and eventually (fix and) use it properly.
KeyboardAvoidingView the Missing Docs
If you are struggling with React Native's KeyboardAvoidingView and it does not behave as you expect, the most probable reason is some flex layout issue. I highly recommend reading
KeyboardAvoidingView not working properly? Check your Flexbox Layout first
by Nick Yang.
Continue reading →
This is a collection of things I sometimes need when working with React Native and my external Android device.
Continue reading →
React Native has a component Pressable. Used like so <Pressable>clickable thing</Pressable>. It is a more abstract way to build a button or something that a user can click. The component Pressable has one Android-specific attribute android_ripple, which allows to customize the UX of the ripple effect. I think the visual feedback the ripple effect provides is very user-friendly, it indicates if a click was detected. So I am investing time in making it work well, but it's not that easy. Let me share my learnings.
Continue reading →
The plan:
Theme.AppCompat
https://developer.android.com/guide/topics/ui/look-and-feel/themes?hl=en#CustomizeTheme
Continue reading →
I never did android development, only the React Native side of things. Now while digging deeper, trying to figure out how to style a React Native picker on android (because the default is really ugly) I am reading into android docs. I found out how to break my app's rendering with one line of XML. Not true, five lines of XML.
Continue reading →
Theme.AppCompat is supplied by the Android Support Library
When I started digging into the styles.xml file of our React Native app I found XML like this:
Continue reading →
I want to use my real android device to preview stuff, not the emulator anymore. If I don't get the CPU power I need, I need to work around it.
Continue reading →
I was just struggling to find out how to start a different emulated Android device from the command line. I found the relevant commands:
Continue reading →