Review Platform Fit

Review Platform Fit

Platform Fit Matrix

A platform shortlist should be reviewed against constraints that can be measured or inspected. Use the matrix to record what each candidate can prove and where it may hide risk.

Figure 1 compares platform choices by the proof they can retain.

Parallel ESP32 DevKit and Raspberry Pi evidence panels compare roles, timing, energy, communication or service recovery, and hidden risks. Pi GPIO example commands one second high and two seconds low for five passes; lower strips name evidence areas and decision steps.
Figure 1: Hardware platform evidence matrix linking platform constraints to proof and hidden risk

Compare the parallel ESP32 DevKit and Raspberry Pi panels by role, timing, energy, and communication or service recovery. The ESP32 panel asks for boot, wake, and radio-attach measurements. The Pi GPIO example commands one second high and two seconds low for five passes: 15 seconds of commanded delay, not a measured timing guarantee. Energy and recovery entries distinguish endpoint sleep and link loss from gateway idle power, storage, and restart behavior. Hidden risks differ too: USB-UART and regulator circuits can mask ESP32 sleep current, while Pi hardware and its software image affect idle power and recovery. The lower strips name six evidence areas, then require measurement, a rejected option, and a next gate.

Review these evidence areas:

Timing evidenceDoes the platform expose timers, interrupts, reset behavior, and diagnostic logs needed to measure response?
Energy evidenceCan active, idle, sleep, wake, and failure states be measured separately?
Communication evidenceCan the prototype test the real message path, retry behavior, link loss, and gateway boundary?
Physical evidenceCan connectors, mounting, sensor placement, service access, cable strain, and enclosure fit be represented?
Software evidenceDoes the toolchain, library layer, update path, and debug route match the evidence the team needs?
Transition evidenceWhat must change when moving from this platform to a carrier board or custom board?
TipShortlist Rule

Keep at least one rejected option in the review record. A good platform decision explains why the chosen form fits now and why a plausible alternative was not selected.

Back to the chapter