mobile: generate profile tab icon from user sigil

[alecananian]

PR Checklist

• Includes changes to desk files
• Describes how you tested the PR locally (test ship vs livenet)
• If a new feature, includes automated tests
• Comments added anywhere logic may be confusing without context

Changes

• Updates profile tab icon to be an Urbit sigil for the logged in user's ship
• Fixes Tamagui dark mode

Note: very simple implementation for now that doesn't have all the different sizing and color options we'll need. We can address the sizing when we start to use the sigil component on other tabs, and the colors when we get contacts syncing hooked up.

[linear]

LAND-1543 Port sigil renderer to RN

[dnbrwstr]

This looks great! What do you think about moving the sigil wrapper to the shared ui lib? Seems like a pretty core component.

[dnbrwstr]

Looks good, just a few comments on styling consistency.

[dnbrwstr]

Although re-reading the above, maybe you're just wanting to hold off on styling w Tamagui until we build out a bit more -- fine with me if that's the case.

[alecananian]

This looks great! What do you think about moving the sigil wrapper to the shared ui lib? Seems like a pretty core component.

For this, do you think we should move the memoized XML to the shared lib? The full component probably doesn't make sense because it's React Native-specific.

Although re-reading the above, maybe you're just wanting to hold off on styling w Tamagui until we build out a bit more -- fine with me if that's the case.

That was my initial thinking, but lemme dig into the Tamagui side a little today and see what I can do here 🙂

[dnbrwstr]

For this, do you think we should move the memoized XML to the shared lib? The full component probably doesn't make sense because it's React Native-specific.

Ultimately, the goal is for the ui package to export interfaces for core components, so that they'd be importable in other contexts (for example, another prototype/testbed app). It could export a sigil component that in the long run could be backed by .native.ts and .web.ts implementations, but for now could be native-only.

That's a secondary goal though, so feel free to ignore if it's laborious.

That was my initial thinking, but lemme dig into the Tamagui side a little today and see what I can do here 🙂

Cool :)

[dnbrwstr]

Changed to approve since I don't think either of these are blockers.

[alecananian]

@dnbrwstr I've updated this to use Tamagui now
I haven't changed anything to do with the size and space - let's address that if/when we use this component anywhere else

[dnbrwstr]

Great, this looks good! I'm going to go ahead and merge.