The writing, which I started with the iPhone’s manuscript, moved to Scrivener after its debut, and moved to the novel-writer, a plug-in for VS Code, during the Corona disaster. It was an environment that each had its own reasons and attachments, but I started thinking about moving this spring.
It was the AI agent who pushed my back.
Development support using LLM has been used for novel-writer refactoring and LLM conference systems, but the generation has changed and we have been able to create full-fledged native applications.I tried the Champolion Deck of the Web View app, wrote zen Babel and FM-Deck, a native macOS app made with Swift, and thought that I could make my own editor for work.I know it’s not sweet, but I have a dream in a vertical writing-compatible writing environment that can use Apple Intelligence, a local AI, as a helper.
That’s what I thought of last week (23rd) on Thursday afternoon. ChatGPT and specifications began to be implemented around 15:00.Step by step, we can now build vertical editors for iOS and macOS before dinner with little backtracking.
It may sound like it went very smoothly, but there was some stress. The most difficult thing was the assumption of ChatGPT.
Vertical writing-compatible editors that work on iOS and macOS? In other words, it’s an editor that runs on mobile and PC.Then there is no doubt that it is Electron (an application platform that uses Chrome’s WebView). WebView also supports vertical writing. Git is also necessary. Okay, then let’s put it in from the node module. React Native is also good.If you don’t like heavy things, Tauri is also available. Yarn is like this–
I don’t know how many times I stopped saying let’s calm down. I didn’t expect to be hit by such a proposal full of halcination in 2026.Electron and Git don’t work on iOS, and I don’t understand why they propose a huge luxury platform for compatibility even though they say “on iOS and macOS”.
After communicating for about an hour, I managed to write an agent.md to create a Swift native application.I knew that AI development would be dragged into a common implementation, but if I didn’t do it quite consciously, I didn’t know what would be screwed. In fact, after this, “Is it Version 1? That’s good, I’ll put in Git! Or “It’s a vertical rendering, I understand.Suggestions such as “I’ll put in GhostScript and TeX” will continue. When a developer who has just joined a project says “I understand” at the first time, it is usually wrong, but the AI agent replays it excellently. If you are developing AI, you should take a look at the project once.
Even after it starts to move, Codex wants to plug in status monitoring every time it makes a request. Changing the size of the window, editing, changing the status, etc.These processes are executed asynchronously, which runs behind the user’s operation, and from around Codex 5.2, it avoids at least a collision of functions, so the app itself runs, but the monitoring that is applied tenfold and twentyfolds worsens the application experience. Return it to a design that moves without surveillance and have the hole blocked.Repeat this to improve the experience, and the resilience design is implemented in tight code. When you find a function that can be separated, divide the branch and stack the history of git at the time of sure progress. If this happens, AI agents will also become smarter.
A few days after starting to move.At the moment, with has grown into an editor that can adjust the line spacing and edit vertically and horizontally in the Japanese beta group 2. It has become an application with a multi-window (this is also something that AI did not do well.Because there are many single-window applications now), the scroll bar is also displayed (AI will try to delete it immediately). The vertical writing of iOS, which is implemented by itself, can now be mixed with Japanese and European (no matter how many times AI says it, it will do its best to make the ascii, which is drawn horizontally, into a full-width vertical group).And you can now marquee the markdown heading and the blue sky bunko’s ruby. Markdown bold is bold, and side points are not yet supported, so it is a marquee.
Because it has fewer functions than the standard text edit, the operation itself is light. The video below is about opening the full text of “Man Kind” (230,000 characters), but it is a speed that can be tolerated to change the layout by changing the width of the window, and there is no stress in scrolling or editing in the middle.This is because NSText on macOS has an asynchronous long sentence layout evaluation. If it is written vertically, the drawing will be missing in this layout evaluation, so there are some places where you can’t leave it to the OS, but I’ve thought of several ways to solve it. It will be manageable.
It’s a little impressive that the markdown headline and the blue sky bunko style of ruby are appreciated. Yesterday, I implemented the typewriter scroll.
I would like to move paragraphs and words today or tomorrow. If you make it like this, you will gradually grow into an editor you have never seen before, but since it is an application that I am making for use, you can make it as you like. Even on iOS, if you connect the keyboard, you aim to run as well as macOS.I’ve been using XREAL recently, so I want to make it compatible with extended displays.
I also want synchronization using iCloud and Git-style history (it’s cumbersome and heavy to put git on iOS), and a red and pencil-style refinement editor. I’m making it myself.
It is difficult to say that it is stable, so I can’t release it yet, but I’m thinking that everyone can use it eventually.
Oh, that’s right. We are looking for Git sponsors.
