Try it here: https://czmanix.github.io/pebble-color-optimizer/

If you are developing for Pebble, you can use this app to create more lifelike image of what you wanted in the first place.

Upload your image in 200×228 (larger will crop) with photo or UI elements to test.

This will create an image for the export, that will look the closest to your input on the real watch. Maybe ugly on a normal monitor, but nice on the watch. You can tune brightness and contrast to get most colors from your input.

It supports Atkinson dithering suited for photos, or 50:50 multicolor dithering, which is better for UI elements.

You can use your own sun/room/backlight palettes by replacing the PNGs with your own.

Everything is here: https://github.com/czmanix/pebble-color-optimizer

This is a follow up to this browser extension: https://www.reddit.com/r/pebble/comments/1unfeel/pebble_real_colors_view_watchfaces_and_apps_in/

While choosing my next watchface I don't know, how those fancy colors in the App Store will look on the passive display of my Pebble Time 2. So I took photos outside inside and in the dark with backlight on of all the available colors, created custom palettes and vibecoded a browser extension for simulating these conditions in the App Store.

Everything is at https://github.com/czmanix/pebble-color-extension/ This is the readme.md with instructions:

Pebble Screenshot Color Corrector

A browser extension for Google Chrome and Microsoft Edge that adjusts the colors of Pebble smartwatch screenshots on the Repebble App Store to match their real-world appearance.

Pebble smartwatches use a color e-paper display that looks different depending on the ambient lighting. Developers usually upload screenshots using the "ideal" pure RGB color palette, which can look overly saturated on a computer monitor. This extension maps those ideal colors to real-world palettes derived from actual macro photos of the watch.

Features

• Multiple Lighting Modes – Switch between Original, Sunlight, Room (Indoor), and Night (Backlight) color profiles.
• Seamless Integration – Automatically processes and recolors screenshots directly on apps.repebble.com.
• Instant Reload – Changing the mode in the extension popup automatically reloads the current tab to apply the new color palette.

How to Install

Since this extension is not published on the Chrome Web Store, you can easily load it as an "unpacked" extension:

1. Download the code: Clone this repository or download it as a .zip file and extract it to a folder on your computer.
2. Open Extensions page: In Google Chrome, go to chrome://extensions/ (or edge://extensions/ in Microsoft Edge).
3. Enable Developer Mode: Turn on the "Developer mode" toggle switch, usually located in the top right corner.
4. Load the extension: Click the "Load unpacked" button in the top left corner.
5. Select the folder: Choose the folder you extracted in step 1 (the folder that contains the manifest.json file).

How to Use

1. Visit the Repebble App Store.
2. Click on the extensions icon (the puzzle piece) in your browser toolbar and pin the Pebble Color Corrector.
3. Click the extension icon to open the popup.
4. Select your preferred lighting condition from the dropdown menu.
5. The page will reload automatically, and all app and watchface screenshots (not animated) will be displayed using realistic colors.

How It Works (Technical Details)

The extension utilizes a background Service Worker to fetch the screenshot image data, successfully bypassing the strict CORS policies on the Rebble servers. The content.js script then draws the image on a hidden HTML <canvas>, compares every pixel against a predefined color mapping table (generated from real photos), applies the corresponding real-world color, and replaces the image source directly in the DOM.

How It Was Created

A simple app for Pebble displays all available colors.
Photos of this app on my Pebble Time 2 were taken by me. Then in Photoshop by sampling average area of a displayed color I've created real world palettes by hand. The rest was vibecoded with Gemini.

Licence: Do what you want with this, have fun, and please give me a credit :)

MK3+MMU2 left, CoreOne+INDX right
same 153 g on the model
281 g vs. 37 g of wasted filament on 2247 changes of filaments
over 70 hours vs 14:45 hours of printing

notes:

• no major issues during the print. The model (https://www.printables.com/model/35-adalinda-multimaterial-remix) requires a tiny support on the front belly, which I forgot to put on, but the print recovered.
• the poop bucket will need a better solution. Quesstimate of its safe capacity is around 3000 changes of filament.
• you can put the PLA waste in a cup and fill it with boiling water to form a more solid object (shown here)

I have been using the Navimow X450 for several months, and now I have access to the new Z120 Lidar from Roborock. Both mowers use the same idea for an independent front axle, and both are AWD. At first glance, the Z120 Lidar looks worse:

• More expensive than the X420 for the same coverage
• Only one cutting disc, resulting in slower mowing
• Fewer options in the app
• Worse display and controls on the mower itself

But after a short hands-on experience, things look different:

It is built like a tank. The Navimow X4 series is not a delicate piece of machinery either, but if I had to bet on which one will last for more years of service, I would choose the Roborock.

The Z120 uses hub motors in each wheel, so it is dead silent – even the turning is quieter and more fluent compared to the Navimow X4. Also, there is no silly string holding the mowing deck like on the X4 and it floats on the lawn just as well. Furthermore, the cutting disc – covered with a free-wheeling metal plate – is better protected than the Navimow's.

If you have a Navimow X4, you have a great mower that should serve you well. There is no need to return it and go for the more expensive Roborock. But if you thought that Roborock's first entry into premium robotic mowers was dead on arrival due to its price, I think there are reasons why that price could be justified.

As I have a WiFi camera pointed at the dock with my mower I noticed in night vision mode of the camera the mower is flashing its front infrared sensor all the time even when docked and charging.

Isn't it a little bit redundant stressing unnecessarily the sensor? The mower is connected to the pins in the dock and charging, so it knows it is firmly docked. I think a simple firmware fix should fix that.

Experimenting with hand drawn stickers for some personality. "Mouth" is probably good as it is by design.