Search for a command to run...
I'm a developer who grew up in Houston, TX. I've done a lot of things in my life and have finally found that software and development is truly what makes me happy.
I've been a musician, a teacher, a flight attendant, and airline pilot, and now a full stack software engineer.
I get to learn about new tech every day. And I'm here to share it all with you.
No comments yet. Be the first to comment.
Quickly Set Up Your Own Strapi Instance on Fly.io
Boost your JavaScript expertise and streamline your coding process
Develop a Full-Stack Application Quickly Using Next.js and Supabase
Top Practices for Responsive Design in Next.js with TailwindCSS: Full Setup Guide
Next.js for Newcomers: A Clear Guide to Essentials
Meet Hundred Habits - a habit-tracking app I recently published on both the iOS App Store and the Google Play Store. Hundred Habits is based on the Law of 100 principle. If you're not familiar - the Law of 100 is a commitment to a task or a goal for 100 iterations or days. It's about doing something consistently, without fail, 100 times.
My mobile development framework of choice is React Native. I was originally a huge Flutter advocate when the platform was first introduced several years ago, but given that I'm primarily a Javascript / React developer, it makes more sense for me to keep my brain focused on that stack. So React Native it is.
Hundred Habits is simple. There's no auth. There's no account creation. Everything is stored locally on the user's device. It's simple enough that everything could probably be stored in local storage as JSON strings, but I wanted to play around with WatermelonDB and SQLite.
Why not just use SQLite directly? What appeals most about WatermelonDB to me is the speed. The number one goal of Watermelon is real-world performance. Watermelon is fast. Loading a full database of tens of thousands of records onto a mobile device is expensive. According to their docs, Watermelon fixes this by being lazy. Nothing is loaded until it's requested.
Another huge advantage of Watermelon is that it's fully observable. Whenever you change a record, all UI that depends on that record will automatically re-render. (Well... almost automatically). You just need to wrap your components in a way that allows them to observe changes.
const Comment = ({ comment }) => (
<View style={styles.commentBox}>
<Text>{comment.body} — by {comment.author}</Text>
</View>
)
// This is how you make your app reactive! ✨
const enhance = withObservables(['comment'], ({ comment }) => ({
comment,
}))
const EnhancedComment = enhance(Comment)
I did run into a few challenges while setting up the project. The first big challenge was that I use Expo for my React Native apps. The Watermelon docs don't really have any Expo-centric instructions so I had to do some googling. Luckily, this plugin exists, which makes configuring Watermelon in your React Native Expo project a breeze.
It's as simple as installing the plugin and then adding it to your app.json .
Install:
yarn add @morrowdigital/watermelondb-expo-plugin
Add the plugin to your app:
{
"plugins": [
[
"@morrowdigital/watermelondb-expo-plugin"
],
[
"expo-build-properties",
{
"android": {
"kotlinVersion": "1.6.10",
"packagingOptions": {
"pickFirst": [
"**/libc++_shared.so"
]
}
}
}
]
]
}
After that, I had to run a npx expo run:ios and a npx expo run:android in order to get all of the native libraries installed. Adding custom native code is covered in this guide from Expo.
The people at MorrowDigital also have this great article for getting everything set up.
Here's my github repo for this project. If you have any question, please comment below!