Thegabbanator

Sounds good @coolsoftwaretyler, just made another small change and removed the unneeded android section from the config plugin after some more studying. Feel free to adjust the code names, etc....

Also I apologize, I somehow back tracked a release ci PR.. my bad. Idk how to undo that part.

Hear me out @coolsoftwaretyler / @frankcalise, I feel like the Activity / Suspense boundary mentioned above feels like it doesn't include preloading other things like auth, i18n, navigation state, etc.....

Okay @coolsoftwaretyler / @jamonholmgren, I think I found a clean approach that allows you to only have to handle the fonts in one place for ios, android, and web. Basically:...

Okay @coolsoftwaretyler, great comments. I actually figured out a way to rename the files and make all the platforms line up on the file imports! Seems to work great! Check...

Did I do it? haha never rebased before.

Awesome! I've been experimenting with different fonts on import and there's definitely some insistency between different fonts. There may be some fonts where we need to use Platform.select still. Montserrat...

@coolsoftwaretyler No, I'm just using Monserrat in my personal app, but I have to differentiate between the iOS and android platforms for that particular font. Note how I'm importing them...

Whoa I just figured it out, do not merge this. By following the rules of hooks, I masked the error: ```tsx export const useCustomFonts = (): [boolean, Error | null]...

There we go, now its consistent with mine, you do need to use Platform.select on ios I was wrong, when I fixed the hook per your recommendation, it was dynamically...