I have to admit that I didn't really think about reminders. That would perhaps make more sense for Simple Calendar, perhaps in the future I might consider linking notes and reminders. Or maybe it would make sense to implement it directly in Simple Notes? I don't know, I'll keep that in mind for later, thanks!

the number of clicks/menus/presses it takes to create a note

I strongly agree on that. It must be at most as many clicks as on Google Keep, i.e. two clicks (plus a few to open the app).

import existing Keep notes from a Google Takeout into your Simple Notes

I didn't think about that. That shouldn't be too hard. After the MVP (minimum viable product) will be ready, imports from various common formats should be implemented, and I guess Google Takeout for Google Keep should be supported too.

Thanks for the suggestions!

Whoa, that's a long list of ideas... let me see...

1. That's the plan, excluding iOS as I do not have a Mac and thus I cannot develop for it
2. Certainly
3. Certainly!
4. That's not part of the MVP (minimum viable product) I have in mind, but an export function must certainly be added later
5. Plug-ins are not part of my goal, but I will do my best to keep the source code modular enough to let people adapt it freely
6. We agree on that, global search is necessary, but I did not think about a "search inside a note" option. That seems to make sense, I'll see what I can do
7. Tags are part of my idea, although not the MVP, but folders are not; I will see if I can also add folders without complicating code and UI too much, that doesn't sound like a bad idea
8. Not part of my goal, but maybe in a future iteration
9. Yup, that's what I had in mind too
10. As a developer I like Markdown, but it is not on my priority list... perhaps in a future iteration. I was thinking to (maybe) use Markdown behind the curtains, so it might not be too difficult to let users toggle the WYSIWYG
11. The first UI that I am planning to develop will be for the web browser, then a lazy-man Electron UI for the desktop as well as something for Android, I just wanted to do something simple. I don't have the time and skills to do deep desktop integration, perhaps in the future, or maybe someone might contribute this feature if this project actually manages to become something interesting
12. That's not part of the Simple Notes app I was thinking about, but that would make sense for Simple Calendar, perhaps in the future I might consider linking notes and reminders, but that's not something I am thinking about yet
13. I did not think about that, that's a good idea, I'll see what I can do
14. The first version will not let you upload media, but images are planned. I did not think about sound/video/documents, but I guess why not?

I think notes collaboration might be a anti feature

That's the main reason why I decided to build this suite of apps in the first place. I want to be able to work collaboratively on things with my girlfriend, and we must be able to do it in real-time. I realize that this will eat away a big chunk of the total time I will dedicate to this project, but it is also the main reason why I am not satisfied with the options currently available.

Oh, I like this a lot! I will consider adopting it if I will actually get this project started. Thanks!

Then what's even is the point of this license? There will always be a third party distributing unofficial binaries.

And if this license forbade third parties to redistribute binaries, then it would no longer really be FOSS.

Iirc I had a Windows 7 (maybe 8 or 10) Home OEM, original (not cracked), but it still worked. Perhaps if I had kept using it for long periods in the VM it would have started complaining? Anyways I booted it baremetal from time to time, so maybe that's why it kept working.

We do have a federated GitHub alternative. Perhaps not too mature yet, but it does indeed exist. Forgejo

Do you happen to own one? If yes, how do you feel about it?

For example, in the PineTime there is a heart rate monitor, but it's too slow and imprecise. Notifications work great, and the battery lasts 20 days or more. How about the Bangle.js 2?

I am not sure... in the case I'm referring to, they were lagging also when scrolling. But it was React, so native browser rendering. And they were actually very large tables, so we had to do some funny things like viewport culling (see react-window).

For what it's worth I've never had any similar performance issues with tables in Flutter (web with the canvas-based render engine, not Android) when applying the same culling technique, they just ran fine at any resolution. Different hardware, though, so it's not an apple to apple comparison.

In any case just to be safe I would personally assume less pixels = less work = less power = more battery life. My opinion is very unscientific though.

Isn't rescaling usually done by the display driver? I am fairly certain this is the case for external displays. Are laptop displays any different?

Edit: with "display driver" I mean the hardware chip behind the display panel, dedicated to converting a video signal to the electrical signals necessary to turn on the individual pixels.

As a web developer, I noticed that some elements such as very big tables struggle to render on 4K but are absolutely fine at 1080p. I would assume that means the CPU and/or GPU are more taxed to draw at higher resolution, and therefore I assume they would draw more power. I might be mistaken. Do you speak by experience?

Good separation between business logic and UI without effort, cross-platform UI in any language, possibility to turn it into a web-accessible service in the future, great choice of UI frameworks and battle-tested components if you decide to go for a web framework and language.

As an example of a successful software that followed this approach: Synchthing. All versions run a local web service in the background. The Desktop version just opens a browser on the index page. The Android version is a native app that calls the exposed REST API on localhost, bypassing the web UI.

As an example of a much more complex software, albeit not FOSS: EasyEDA. It's a web software, but it also comes as a desktop app (which I never tried) which I assume is not much more than a frame for the web view.

My recommendation: write the UI with React on Vite in TypeScript, and write the business logic in your general purpose language of choice (mine would usually be C#).

I'm glad it's working! Yeah, right after posting that message I also noticed they forked it with a new name.