--- tags: learn --- # Dev Rel Oh, so caveat that I’m still learning-- if I had to think of important stuff it would be We’re increasingly consumer-facing. We’re creating that consumer-facing aspect not just with Magic Wallet Dapp, but also in how we’re discussing how a user can manage multiple wallets (this is “Magic Auth to Magic Connect Interoperability). Like with Fortmatic -> MC, we’re trying to consolidate a bit. I think Dev Advocacy is sort of important here, in that I think some of the designs and features come from the perspective of “We’re attracting Web 2.5 clients” and not “We need to fight for the loyalties of die hard web 3 users.” I don’t feel Magic is always clear on this. We’re developer facing, but I don’t know if we’re very intentional about it. I think MWAS might be our only API as a service thing. But don’t have a versioning strategy, really. We do have our SDKs and are mindful of backwards compatibility and whatnot, but that’s it. Then there’s EEIP-1193, which I think might have impacts on that. https://dashboard.stagef.magic.link/app?cid=9JbZOVH0_eF75oqDYEGLN08BM_pyPFhtCTIzQ1UcgqQ= is (one) of our test dashboards. (We also have a dev one). So you can do some playing around with it. We also have something called “Relayer,” which is “Phantom,” which is basically our SDK. There’s also a dedicated test page for “Relayer,” which allows you to interact with the iFrame flows.https://auth.stagef.magic.link/e2e . There’s also a (sorta not great) page about setting up these services totally locally. It’s buggy so not sure I’d recommend, but we can. Joe also made this set of testing things for direct use with the API https://github.com/magiclabs/insomnia-sync https://github.com/fortmatic/fortmatic is the backend monolith https://github.com/fortmatic/phantom is the fe iframes https://github.com/fortmatic/magic-dashboard is the dashboard code 12:00 Oh, and for poking around the DB… you can connect via these creds. https://github.com/fortmatic/fortmatic/blob/6662fac95ee8b6eeb49bc710ee2c92b332c0bfd8/fortmatic/config/env/db/topology.yaml