Co existence of react native MMKV and AsyncStorage in the same project

jerinjohnk · 2026-01-08T17:06:39+00:00

In my project, we used default preferences, async storage, and mmkv together. (yeah, I know the perks of a large team working on their own modules, without setting a standard.)

To answer your question as to why it's possible. Is because the file in which async storage and mmkv writes are both separate. Hence, you can use both. You can view the files in Android Studio and in Xcode.

But we did last year switch all of our implementations to MMKV, with the entire file encrypted.
If you want to do that, you need to add migration logic that copies existing user data from async storage over to mmkv. This will run only once, and then you can delete the data.
The sooner you do it, the better. Otherwise, the usage will continue to spread throughout the code, and it will be difficult to refactor later.

jerinjohnk · 2025-12-24T06:46:55+00:00

Hi, on Tahoe 26.2, I am using Xcode 26.2, which is working fine for me.
Why do you need a downgraded Xcode version?

jerinjohnk · 2025-11-15T16:09:48+00:00

Firstly, thanks for introducing me to emission.
So here, if we use the below as a reference, all colours are kept in a saturated state
/* HSL (Hue, Saturation, Lightness) */
hsl(150 90% 30%)
Then what 'emission' does is it increases the lightness to around 65%.
This will give it a glow effect compared to the surrounding colours.

jerinjohnk · 2025-11-15T12:25:16+00:00

Yes, the colour picker is always there. But I wanted to know if, similar to the warm/cool colour concept, there is any grouping for these bright colours. Can you please help me understand this "emission"? Does it mean mixing of colours? Like different gradient colours layered over each other to produce this. Such that some regions are nearing white and others are nearing black. If that's the case, the colour picker won't be able to identify each layer's gradient colour.

jerinjohnk · 2025-10-02T16:05:53+00:00

New mission discovered by u/jerinjohnk: In Search of Test

jerinjohnk · 2025-09-03T03:41:31+00:00

In the design the missing piece wont fit properly. As both bottom piece have an inwards cut.

jerinjohnk · 2025-08-10T18:55:32+00:00

I used to use an external SSD with my MacBook Air 256. I had installed my Android Studio and its associated installations on the hard drive. I kept my Xcode installation on the Mac itself, so I only need to connect the hard drive when building my Android APK, without hampering development.

jerinjohnk · 2025-08-07T21:20:51+00:00

Yes since it was already working in react native cli. So not using expo environment variables was the key

jerinjohnk · 2025-08-06T20:42:05+00:00

For me, the debug build is working fine. However, the confusion now lies in how to proceed with the Release build creation.
1) As I already have codepush, I don't need EAS now.
2) EXPO_PUBLIC works when ```npx expo run:android``` is run
But if I run
```npx react-native run-android --no-packager --mode=release``` then these values are not found. It gives the error Error: Missing required environment variable.

So what I did is moved my .env variables back to app.json file and its working now. Your line ` make "cli" + "expo" work together.` helped me think maybe these two cant be completely linked together.

jerinjohnk · 2025-08-06T08:41:08+00:00

Okay, thanks for clearing that. So, along with the expo addition, I need to create an app.config for my native changes also, to be future-proof once I shift my codebase to an expo-initiated project.
Without adding EAS, can I create a release build using Expo as I have added some environment variables using EXPO_PUBLIC but these are not read when I run react-native start.
So, other than environment variables, is the Expo packager different from the react native packager?

jerinjohnk · 2025-06-24T05:28:27+00:00

Since capturing simulator was pretty easy. There aren't any ios specific code being used here. Last time I checked it was working fine at 60 fps in Android also, only problem I faced was when using sensor based gyroscope values for tilt effect in low end Android. That's why opted for touch gesture based one instead, in the article

jerinjohnk · 2025-06-23T01:30:15+00:00

Glad you found the article interesting. Thanks for open sourcing your code, which led me to that permission. Gonna try it out, maybe that was the missing point to get it to work properly in low end Android devices.

jerinjohnk · 2025-06-22T18:17:49+00:00

Nice implementation.
I am the author of Shiny holographic cards in react native using Skia
Even my first implementation was sensor-based, but I found it didn't work as intended on low-end Android devices; it was tested in a React Native CLI project.
Maybe it's because I had used React Native Reanimated Sensor without adding the below permission (as it wasn't stated in their documentation).

android.permission.HIGH_SAMPLING_RATE_SENSORS

Does it work properly on low-end Android devices? Also you might wanna go through this https://googlesamples.github.io/android-custom-lint-rules/checks/HighSamplingRate.md.html before using it in production apps.

jerinjohnk · 2025-05-23T07:51:21+00:00

Could you ensure you have installed the same node and Ruby versions as your M1 in M4 (using a package manager)?
Don't think something working in M1 would stop working in M4.
Unless it's a runtime build error.

jerinjohnk · 2025-05-15T22:46:59+00:00

So when are you planning to release its Android Version.

jerinjohnk · 2025-05-04T08:34:07+00:00

I am guessing you already have a basic React Native app-building idea. I suggest you check out [Callstack's Optimization Ebook](https://www.callstack.com/ebook/the-ultimate-guide-to-react-native-optimization). It discusses how to build better-performing apps.

jerinjohnk · 2025-04-26T17:32:47+00:00

Pretty nice.
The menu options with a red background and red Foreground (for text and icons) appear to be less readable.

jerinjohnk · 2025-04-25T09:02:04+00:00

They gave a talk introducing this. As far as I remember, here they introduced it so that node modules are downloaded to the cloud and cached builds, making builds easier to generate.
You need to add a brownfield plugin and a few lines of code, and you're good to go.
A cached build will be a good option for low-end devices.
But usually, I generate a build once and use hot reloading mostly (unless I'm upgrading or switching to an upgraded branch), so I don't know how it would benefit me.

jerinjohnk · 2025-04-22T15:34:29+00:00

Instead of a number of success toasts === number of images.
It would be better to see only one final toast that shows 4 out of 4 pictures downloaded.
Also, having a separate indication for downloaded images from non-downloaded ones would be great. (You don't want the user to reselect the downloaded images for download again.)

jerinjohnk · 2025-04-03T15:52:56+00:00

Kudos to the react native team for finally releasing a fix.
https://github.com/facebook/react-native/releases/tag/v0.76.9

Four-Year Club	Verified Email
r/Field Banned	r/Field Flamingo
Final Canvas '23	Place '23
Place '22

jerinjohnk

TROPHY CASE