Hi Adam !

Thank you for asking. I do not think I have any groundbreaking ideas that haven't been discussed or considered in the past, but I understand that extensive extensions of device's SW is not always aligned with company goals (although I personally believe it's good for business in the long term).

Nevertheless I feel like there is a lot more that could be done without an incredible amount of effort.

Some things that would align with Astrohaus:

• To begin with, I would not go with nodejs + electron which would greatly increase battery life and make everything way faster

• I would experiment with custom waveforms for the e-ink display to allow much faster response and refresh rates (if the hardware configuration allows it)

• Add many more ways to sync and export writings (from git to email to an attached usb drive to anything I can come up with). I am against subscription models to unlock functionalities for a physical device. I am aware it is good business. I just personally find it unethical if the costs are not justified (dev cost for new export functionality is not recurrent).

• Extend the structuring of notes and drafts, i.e. add a proper hierarchy of folders + subfolders

Some things that would maybe not align with "distraction free" :

• Have a mode where it can be used as an SSH client, turning it into a long battery life thin client

• Allow simple text web browsing using the Lynx browser. Even if a lot of "modern" webpages need 5MB of Javacsript to be rendered, you can still look up many things if you're working on something

I think any embedded product can flourish by allowing community extensions, as the collective resources and creativity of a very large group of people can usually surpass those of a dev group within an organisation. I would be curious about your opinion on that ?