Switch
Switch to Palpable from Arduino
Arduino is where most people learn hardware, and it is excellent at that. People move to Palpable when the goal stops being “learn to write firmware” and becomes “I just want this device to work” — describe the behavior in plain English or by voice, and PAL writes the code, deploys it to a Raspberry Pi, and runs it. You are not replacing the craft of embedded code so much as skipping it when it is not the point.
What you stop doing
No more hand-writing sketches, wiring breadboards, or flashing a board every time you change a line. You stop maintaining the loop, the pin config, and the libraries that go with each new sensor. You describe what you want to happen and let PAL produce and run the code.
What stays the same
The hardware mindset carries over completely. You still think in sensors, thresholds, and actions, and you still own real code — scripts are TypeScript, not a black box. Every project exposes REST and WebSocket APIs plus a CLI, so the tinkering instinct Arduino taught you still has somewhere to go.
A typical first project
Plug a certified Qwiic module — a temperature or motion sensor, say — into a Pi Zero 2W. Tell PAL “warn me when this room gets above 26 degrees.” PAL detects the module, writes the script, deploys it over the air, and it runs locally on the device, even if the cloud drops. No soldering, no sketch, no re-flash.
Where it pays off
The gap between idea and working device shrinks from an evening of wiring and debugging to a sentence. When you want to change behavior, you say so and PAL ships it over the air with automatic rollback if something breaks. The Discord community is a good place to see what people are building this way.
Questions
Do I throw away what I learned in Arduino?
No. The way you reason about sensors, timing, and actions transfers directly. Palpable just removes the parts you may not want to keep doing by hand — writing the firmware, wiring boards, and re-flashing.
Can I still get to the code?
Yes. Scripts are TypeScript and run offline on the device, and every project exposes REST and WebSocket APIs plus a CLI. You are never locked out of what PAL writes.
When is Arduino still the better choice?
When learning embedded development is the goal, when you specifically want a microcontroller like an ESP32 or AVR, or when you want to own and hand-edit the firmware yourself. Palpable runs on a Raspberry Pi and writes the code for you.