Working on our docs and want to distinguish between features built into the wallet by default vs. ones that require the developer to do something. Does this distinction make sense? Is there a clearer way to frame it?

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

optional is a good word, I read it and I understand that I need to do something to enable it because it is no included by default, extra is a good word too

integration is too generic, when I read it, I don't know what it means instantly 

(tho, something like "dev enabled integrations" may work fine, it also says to me that I have to do some work to integrate something to get it enabled)

extensions may get confused with a browser extension

hmm, yeah thinking like "developer enabled" "integrations" as alternatives

How can we urge people to not use their smartphones as passkeys? Totally understandable for small sums but if someone has a large stack they should use a physical key like a yubikey 

Many won’t understand the repercussions

I would replace "core" with "default", just because it's already a well established term

1) Built in (default)
2) Custom 

Could also add an estimated time to implement with different symbols @wilsoncusack