@marlinz008 I thought about such an experiment as well with one very particular use-case: mobile capture.
I was using #Orgzly Revived which has its issues with larger Orgdown files and this overcomplicated sync cascade causing Syncthing conflicts all the time.
I was using it for read-only access to my Orgdown files + mobile capture in one inbox file.
Then I started with #Orgro in parallel just for the capture process so that I don't rely on Orgzly's ultra slow sync process to finish on each capture.
Since Orgro has very weird behavior with shared content (basically I wrote Elisp functions to fix the format for all different kinds of capture content types), I thought about vibe-coding my first Android app just for the capture process in a text file in the format I want.
Not high on my prio list. Let's see how that goes. #ClaudeCode is removing features or adding very annoying stuff so I might as well end up with no proper #AI to do this.
