The Adafruit Feather and FeatherWing System

I'm not sure why you're being downvoted. You're misguided, but have reasonable questions!

Here's the deal for me, cost-wise. I can go on Sparkfun, Adafruit, Digikey, Arrow, etc and get these known compatible pieces of essentially Lego that already have firmware support/libraries ready to go. Digikey (who stocks both Adafruit and Sparkfun parts) will have them on my doorstep tomorrow morning. Using the existing libraries, I'll have the a skeleton of a system up and running by tomorrow afternoon. I'll have the prototype up and running in 3 days.

Then, if everything seems to look like it's going to work well and I want to pursue the project further, I'll fire up Eagle or CircuitStudio and lay out a board. Upload it to Macrofab and wait 3 weeks for my fully assembled boards to arrive. And then port the firmware from my prototype over to the assembled boards. Or rewrite the firmware, depending on the quality of the specific sensor libraries.

It's all about bootstrapping the process. When I get a board from Adafruit or Sparkfun, I've got a pretty good belief that it's going to be high quality and fit well within their existing ecosystem of parts and libraries. Building a prototype out of those parts helps de-risk the project and accelerate the project by cutting out most of the up-front dicking around to get it working.

Plus, the vast majority of these boards also have schematics and part numbers provided. When I go to design a real board, I'll use those as references.

Their form factor places literally no role in their compatibility.

If with a Feather/Wing combo you don't need to worry about 5v/3v, if there wasn't an enforced shape that would not change in the slightest.

> All Feathers and Featherwings use 3.3V logic - so do not make anything that requires 5.0V logic. You must accept and emit 3.3V logic on any Feather/Wing (except for Analog inputs)

Like, the literal shape of the PCB has nothing to do with their compatibility, rules like do.

Same with SPI pins, RX/TX, etc:

> Bus Pins

> To make it easy to create add-ons, we have fixed inter-chip bus pins:

-

The main change vs female headers is now you're forcing beginners to choose something that locks up their hardware.

This isn't a new thing, beginners since Arduino days have been overwhelmed by how shields take over all their pins and often run into clashes.

It's less of a burden if anything to have proper connectors or simply well marked female headers, which newbies can then easily follow between boards.

I mean if even if you're experienced with electronics just try following which pins a board is actually using. You'll need to look up a PCB schematic.

That's infinitely less beginner friendly than simple color coding and fixed connectors.

"Featherwing" is a bit more unambiguous to google than "Wingfeather"[0] at this point.

[0] https://en.wikipedia.org/wiki/The_Wingfeather_Saga