Once you are able to port seedsigner to rpi pico will it be easier to go from there to a ESP32? does the pico have wifi built in?
Sprinting to prep the multilanguage nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3xamnwvaz7tm0venxx6rpd9hzuur4vghsz8rhwden5te0dehhxarj95ezu7n9vfjkget99e3kcmm4vshsqg8je9kf0ajpnffclpx087njugv5vp0psjqfdeh9zuxvukmk0xw5qqu9r45v release in time* for nostr:nprofile1qys8wumn8ghj7un9d3shjtnndpshwmnev4skwetj9e3k7mf0vd5xzaqprpmhxue69uhkxetvd3shytnwdaehgu3wwa5kuef0qyfhwumn8ghj7am0wsh82arcduhx7mn99uq35amnwvaz7tmnv4hxg6t59ehx7umxd3shyefwvdhk6tcpzemhxue69uhkzat5dqhxummnw3erztnrdakj7qpqad0ptuzte83alpkpqqctvewlaqj5zq23c83m82xw8apg4t6zlynsc0nfk4 but in the meantime I'm SO EXCITED to get these RP2350 dev boards in to play with as soon as I'm back from El Salvador!
The hope is that the RP2350 microcontroller will be an easier platform on which to port SeedSigner to MicroPython. Getting us onto a microcontroller (while still fully supporting the original Pi Zero hardware/codebase, of course!) will open up some huge new possibilities.
---
*("in time" actually means "have a preview release to demo" 'cause there's no way we could get a full final release adequately tested in time)
Discussion
Bit of nerd pedantry: Pico is Raspi's dev board for their RP2040 and RP2350 (Pico 2). Pico / Pico 2 run on RP2040 / RP2350 microcontrollers. But RP2040 / RP2350 shouldn't be referred to as Picos.
And these two RP2350 dev boards in the pics above have an optional feature that the Pico 2 does not: additional PSRAM. The RP2040 had limited RAM (264kB) that could NOT be expanded, making it a less enticing option at the time. The RP2350 doubles the onboard RAM to 500kB but adds support for PSRAM expansion. So these third-party dev boards have 8MB on board!
So: RP2350, yes! Pico / Pico 2, no thanks!
As to your first question: sorta. Porting to MicroPython on ANY platform definitely makes it easier to support other microcontrollers. But a big problem with the esp32 ecosystem was its compiler. We got our work-in-progress port compiling for esp32-S2 (after much suffering) but never got esp32-S3 to compile. And even the S2 "success" was just too hacky to feel comfortable with trying to make that a viable path.
However, the future of esp32 is all RISC-V. I would hope that would make the compiler issues simpler (but really have no idea).
AND the RP2350 has two RISC-V cores onboard.
So what works for one RISC-V should ideally be easy to make work on another RISC-V (reality is never so kind, tho).
However... my initial RP2350 work will most likely focus instead on its two ARM cores (tho we'll see).
So... yeah, the answer is: sorta.
Your second question: The Pico 2 and these dev boards have NO wifi / bluetooth on board. There is a Pico W and expectation is that there'll be a Pico 2W soon. But obviously that doesn't interest us (and again, Pico 2 doesn't have the expanded RAM).