Pico Studio displayed on a monitor beside a microcontroller board
← All projects

Personal project

Pico Studio

Aug 2026 · A desktop workspace for MicroPython

I built Pico Studio to keep the everyday work of developing for a Raspberry Pi Pico in one place. Browse files, edit Python, inspect diagnostics and follow the USB console alongside live resource readings. It is a native desktop workspace built with Python and Tkinter.

ABOUT THE PROJECT

A desktop workspace for MicroPython

I built Pico Studio to keep the everyday work of developing for a Raspberry Pi Pico in one place. Browse files, edit Python, inspect diagnostics and follow the USB console alongside live resource readings. It is a native desktop workspace built with Python and Tkinter.

My role
Design & development
Technology
Python · Tkinter · MicroPython · pyserial · mpremote · Pyflakes
Project
Personal project

FROM IDEA TO IMPLEMENTATION

The story behind the build

01

The problem

Keep editing, files, diagnostics and the USB console together during MicroPython development.

02

The approach

Build a Python/Tkinter desktop workspace with explicit device actions, static checks and opt-in monitoring.

03

The result

A desktop workspace for Raspberry Pi Pico development. Gallery readings use labelled synthetic offline data.

My contribution Design & development.

THE MAKING OF PICO STUDIO

Technical notes

01

Connecting listens to the device without stopping its program. Entering the REPL for file access is an explicit action, so opening the workspace does not quietly reset a running Pico.

02

The editor combines line numbers, syntax highlighting, find and local syntax and Pyflakes checks. Diagnostics inspect the text without running it, with a problem list and F8 navigation.

03

The file browser supports uploads, downloads and folders. Folder and ZIP transfers preserve directory structure, validate archive paths and write through temporary sibling files before renaming.

04

Opt-in monitoring keeps the USB console visible alongside MicroPython heap history, filesystem use, CPU clock, device ticks and custom scalar values. CPU clock is a frequency reading, not a CPU utilisation measurement.

05

The gallery includes actual app captures with synthetic offline data and a generated desk mockup. The preview never started the USB worker or connected to a device; its numbers are illustrative, not benchmarks.

START A CONVERSATION

Have a problem worth solving?

Let’s talk about your idea, your team, or the work you’ve seen here.

Get in touch
Kevin Loggenberg

A COLLECTION OF WORK & EXPERIENCE

Expanded project screenshot