Plenty of ESP32 boards come with a small OLED, and plenty come with a LiPo charger. Far fewer ship with both, publish their own battery test data, and arrive with working firmware already flashed. Crescent City, from HW Designs (credited to designer Hao Wen in Hackster.io's coverage), is aimed at that gap. The maker's documentation describes it as an ESP32-S3 development board with a built-in display, protected single-cell charging and a Qwiic connector. It is in pre-launch, and the official docs list it as "Coming soon to Crowd Supply."
This article covers what the maker has published, what Hackster.io adds, and what is still unknown, starting with price.
The silicon and the module
HW Designs' documentation calls the current hardware Board V2.0 and lists the module as the ESP32-S3-WROOM-1-N8. According to the maker, that gives a dual-core 240 MHz processor, 8 MB of flash and Wi-Fi 4 plus Bluetooth 5 LE radios. Hackster.io's write-up gives the memory as 512 kB of SRAM and 8 MB of external flash. The "-N8" suffix means flash only. Neither source lists PSRAM, so readers who need it for camera buffers or large frame buffers should not assume it is there.
Using a pre-certified WROOM module instead of a bare chip is the usual choice for a small-run board. The antenna design and RF certification come with Espressif's module, so the board designer only has to handle the carrier PCB.
The display: SSD1306 over SPI
The main feature is a 0.96-inch, 128x64 white OLED driven by an SSD1306 controller. The maker's docs say it is connected over SPI. That matters more than it might seem. Most cheap 0.96-inch modules use I2C, and an I2C display on the same bus as your sensors competes with them for bandwidth and adds another address to manage. With the display on SPI, the I2C bus, which is exposed on the Qwiic connector, is left for peripherals. SPI also refreshes the full 1 KB frame buffer faster than standard-mode I2C. That helps with animation and scrolling, though for a clock face that redraws once a minute it makes little practical difference.
The docs give the board's height as 13 mm with the display fitted. That is a useful number if you are designing an enclosure.
Power: protected 1-cell LiPo and published runtime
The docs describe charging a 1-cell LiPo through a JST-PH connector from USB-C, at a charge current of about 300 mA. Both the maker's documentation and the Hackaday.io project page describe the charging as protected. The Hackaday.io page also says the project includes published test data, which is less common for hobbyist boards than it should be.
The maker's battery figure is about 24 hours per 1000 mAh running the stock Weather Clock 2.1 firmware, with Wi-Fi turned off between updates. That condition matters. The figure is for a duty-cycled application, not for a board with the radio kept on, and anything that holds a Wi-Fi association or uses BLE continuously will draw more. Treat 24 h/Ah as the best case for this specific workload, not a general rating.
A charge rate of about 300 mA is conservative, which means slower top-ups for larger cells. The maker's documentation recommends a single-cell 3.7 V LiPo of 600 mAh or larger with a JST-PH 2.0 mm plug, matching the polarity marks on the board. As always, check the cell's datasheet and the board documentation before choosing a battery.
I/O and expansion
The maker's docs list these interfaces:
- Qwiic/STEMMA QT connector (a single header, per Hackster.io)
- 2x12 header pins
- Addressable RGB LED
- BOOT and EN buttons
- USB-C
Hackster.io adds a GPIO breakdown that the maker's summary doesn't give: 12 GPIO available to the user, seven of which can also be analog inputs, and three of which are shared with the Wi-Fi radio, meaning readings may not be available when Wi-Fi is active. On the ESP32-S3, ADC2 channels can't be used reliably while Wi-Fi is running. That is very likely the conflict Hackster is describing, but the sources don't name the pins, so check the pinout in the official docs before designing analog inputs around them. Twelve user GPIO is modest for an S3, which says the board is meant as a self-contained display node more than as a breakout for every pin. For more sensors, Qwiic is the intended route.
Size
The docs give dimensions of 70.1 x 25.4 mm, 13 mm high with the display, and a weight of 14 g. A width of 25.4 mm is exactly one inch, so the board will fit narrow enclosures and wearable-style projects.
Software: weather clock out of the box
The board ships with Weather Clock 2.1.6 firmware, according to HW Designs. It also offers an ESPHome 1.1.1 configuration that can be installed from the browser, which matters to Home Assistant users who would rather not touch a toolchain. For Arduino development, the maker names the Arduino IDE with esp32 core 3.3.6 as the supported setup.
The maker's GitHub docs repository has three firmware folders under esp32-s3/firmware: WeatherClock, QwiicSensor and BatteryLogger, alongside an esphome folder. The last two suggest the intended uses beyond the clock: reading a Qwiic sensor onto the OLED, and logging battery behavior.
Hackster.io points out one gap: BLE is not mentioned for the stock firmware. The hardware supports Bluetooth 5 LE according to the maker's spec, but the bundled weather clock is a Wi-Fi application. Anyone wanting BLE will be writing their own firmware.
Licensing: open firmware, closed hardware
The licensing is split, and it's worth being precise about it. According to Hackster.io, the schematic PDF and STEP 3D model are source-available, all rights reserved. You can view them and use the STEP file for enclosure design, but this is not open-source hardware, and you have no license to copy or manufacture the board. The firmware and examples are MIT-licensed, per both Hackster.io and the Hackaday.io project page, so the code is free to reuse in your own projects, commercial ones included.
What It Means for Makers
Crescent City is aimed at makers who want a small, battery-powered, network-connected display node without stacking an OLED module, a charger board and a dev board together. Desk clocks, Home Assistant status panels, sensor readouts and portable dashboards fit the hardware. The ESPHome install from the browser lowers the barrier for the smart-home crowd. The Arduino examples and MIT license make it easy to reuse the code.
What it replaces is the usual three-board setup: a generic ESP32-S3 dev board, an I2C OLED breakout and a separate LiPo charger. Putting the display on SPI keeps I2C free, and the onboard Qwiic port means sensors plug in without soldering. The 12-GPIO limit and the lack of listed PSRAM mean it is not a general-purpose S3 workhorse. Projects needing many pins, camera input or large buffers should look elsewhere.
Availability and price: Crescent City is pre-launch. The maker's documentation and Hackaday.io page say it is "coming soon to Crowd Supply," and Hackster.io describes a planned Crowd Supply campaign. No price, campaign date or shipping date has been published in any of the sources. Until the campaign page goes up, there is nothing to order. As with any crowdfunded hardware, wait for the campaign's stated pricing and delivery estimates before planning around it.