image-gallery VS epdiy

https://www.invisible-computers.com/invisible-calendar/image...

Two:

https://github.com/Invisible-Computers/image-gallery/blob/ma...

Both of these require rendering the content via an HTTP endpoint and both of these currently still require the content to be proxied through the device backend.

> I can buy an ESP32 e-ink screen and run esphome or any of several other open source projects and put a piece of wood on the front of it, too.

Yes, you can! And if you do this, you have absolutely no need to use my e-paper smart screen.

I am hoping to add third party apps, that's why I have created the API for 3rd party apps:

https://github.com/Invisible-Computers/image-gallery/blob/ma...

But right now, I understand that building an app for my platform is

a) more hassle than just pointing to a URL

b) limited upside, because the audience that you can charge for a subscription isn't very big yet.

However, I think that a good app could generate its own audience (aka drive ppl to buy the displays) and then make money by charging them a small monthly subscription fee.

I'll ship within Europe as soon as I have bootstrapped the 7000 Euro necessary for CE certification.

In terms of openness, there is this:

https://www.invisible-computers.com/invisible-calendar/image...

and this:

https://github.com/Invisible-Computers/image-gallery/blob/ma...

I also want to make the esp32 controller itself more hackable in future, but I don't want to promise anything because that's quite a lot of work for me.

Here is the API description:

https://github.com/Invisible-Computers/image-gallery/blob/ma...

And here is the sample app:

https://github.com/Invisible-Computers/image-gallery

Admittedly, I am not the greatest technical writer, but I compensate by being pretty responsive. :)

This display offers a simple API to build applications for it:

https://shop.invisible-computers.com/products/invisible-cale...

https://github.com/Invisible-Computers/image-gallery/blob/ma...

The API doesn't require any special knowledge about e-paper displays, it just expects an image URL in the correct resolution and will then render it to the display.

You can buy the display off the shelf, and if you are interested in building an app, contact me at [email protected] for a developer account :)

Feel free to go to town on it :)

I think the world of homebrow eInk devices is set to take off.

The problem right now is that while the screens have come down in price considerably, the driver hardware remains expensive and proprietary. If you want to build something for cheap, you'll be designing the PCB from scratch (as this author did).

Enter EPDIY, which brings wide support to a variety of screens using commodity hardware. It's still under development, but it's looking really promising: https://github.com/vroland/epdiy

It's based on the old version of EPDiy E-Paper Driver. https://github.com/vroland/epdiy

Looking at the repo, only this example is partially configured for platformio. https://github.com/vroland/epdiy/blob/master/examples/lilygo-t5-47-epd-platformio/platformio.ini

https://github.com/vroland/epdiy this might help you.

I came across epdiy-project recently. It might be helpful. https://github.com/vroland/epdiy

Take a look at this library - https://github.com/vroland/epdiy it may have support for whatever display and driver chip you are using.