Change Details

This diff persists the recently selected emojis from the emoji keyboard into async storage. To create this diff I read through the docs and found these examples right here:

This diff persists the recently selected emojis from the emoji keyboard into async storage. To create this diff I read through the docs and found these examples right here: - [[ https://thewidlarzgroup.github.io/rn-emoji-keyboard/docs/api/useRecentPicksPersistence | API docs for the useRecentPicksPersistence hook ]] - [[ https://thewidlarzgroup.github.io/rn-emoji-keyboard/docs/documentation/Examples/recently-persistance | An implementation example ]] - [[ https://github.com/TheWidlarzGroup/rn-emoji-keyboard/blob/master/example/src/EnableRecently/EnableRecently-persistence.tsx | A more in depth implementation example ]] I believe this should be an acceptable use case of using AsyncStorage (especially as a first step), as we are only storing a small amount of data, this seems like the recommended way to persist the recently used emojis from the documentation, and we are using a completely different emoji keyboard library for web. If we are interested in persisting the recently used emojis across web/native or different devices, then I can create a follow up task for this; however, I personally feel that this wouldn't really add much value to the overall user experience.

This diff persists the recently selected emojis from the emoji keyboard into async storage. To create this diff I read through the docs and found these examples right here: - [[ https://thewidlarzgroup.github.io/rn-emoji-keyboard/docs/api/useRecentPicksPersistence | API docs for the useRecentPicksPersistence hook ]] - [[ https://thewidlarzgroup.github.io/rn-emoji-keyboard/docs/documentation/Examples/recently-persistance | An implementation example ]] - [[ https://github.com/TheWidlarzGroup/rn-emoji-keyboard/blob/master/example/src/EnableRecently/EnableRecently-persistence.tsx | A more in depth implementation example ]] I believe this should be an acceptable use case of using AsyncStorage (especially as a first step), as we are only storing a small amount of data, this seems like the recommended way to persist the recently used emojis from the documentation, and we are using a completely different emoji keyboard library for web. If we are interested in persisting the recently used emojis across web/native or different devices, then I can create a follow up task for this; however, I personally feel that this wouldn't really add much value to the overall user experience.