Agree with this! 1Writer is actually a fairly good solution for capturing ideas — I sync to my vault with Dropbox — but it doesn’t do well for exploring ideas on my iPad. I’ve come to love the Local Graph view to see connections as I’m entering stuff, and miss that when I’m not at my laptop.
My ideal mobile PKM would be Drafts, with a new face, previews, actions and workspaces branded for Obsidian. I think y’all might collaborate with agiletortoise, and wind up with a mature, high powered mobile app real fast. He has been dealing with issues like iPhone configuration for years. (I use Drafts on Mac and IPad, not iPhone.) And I can’t imagine Greg being uninterested. A markdown editor with enormous number of scripted actions, connecting with most anything, Drafts can be very complex. Limited to Obsidian use, it could be much simpler, but still offer easy extensibility.
Note that Drafts is now freemium: free for most, but 29/year for high end features. But given what promises to be land office business for a mobile Obsidian, I’m sure arrangements would be easy.
Of course, a similar option exists for lots of editors. My argument for Drafts is that it is very mature, v25 or so, and was designed as a markdown editor for capturing and doing things with text—sending text to other apps, previewing different flavors of markdown, and so on. So close already to what Obsidian needs, Obsidian/Drafts could be configured very quickly by agiletortoise. Adding and modifying existing actions and so on must be quicker than developing new.
This for me is the primary reason for a mobile version. Typing on a mobile has always been clunky, even with SwiftKey swipe.
But the idea of pruning and refining, really appeals to me, especially using otherwise unproductive time standing in lines and in waiting areas. Thank you.
I have moved from seated desktop work with a keyboard to ergonomic, reclined, comfortable, idyllic work. I have a Pixel Slate wrapped in a comfortable grippy silicone cover, resting on a narrow firm cushion on my abdomen. And I am hooked. For most of my work, I get by fine with voice recognition and don’t mind having to make the occasional correction.
It runs Chrome OS, in tablet mode which means touch screen, but I can create a Linux partition and have done so to install Obsidian. But that Linux partition doesn’t work in tablet mode. So to use obsidian I would have to plug in a keyboard. That means having to sit up instead of sit back. I think Obsidian and any software developer has to decide whether they want the sit back market. It’s going to become an increasingly dominant part of the market, especially with kids, people learning, and those who are never going to be command-line technology users.
I know zip about programming, but would it be possible to port Obsidian as an electron app? I think that is the solution that would let me use it in tablet mode. A pop-up window with markdown commands would be lovely as well. My needs would be simple. Not everybody wants to learn programming commands, even as simple as those in markdown.
*Edit: I was misinformed by something I read which suggested that electron apps worked better in Chrome OS under tablet mode. My mistake.
From what I know, Obsidian is an Electron application, or at least that’s the core framework that it is built upon. Just my 2 cents.
I haven’t used ChromeOS in a while but…you can force desktop mode in ChromeOS and activate the keyboard. Or activate the on-screen Linux keyboard.
I know zip about programming, but Obsidian is an Electron app. How that helps, I don’t know.
Thank you! But I take it that option still wouldn’t provide a microphone button that would allow voice recognition. And voice recognition still isn’t programmable to allow markdown commands (actually I am befuddled by how unpredictable voice recognition is. In some apps it’s better than others, on some days but not others it recognizes grammatical things like semicolons, it is finicky, at least in the Google environment).
- “The reason a right click works in VS Code is that it is an electron app, which is based on chromium. Chromium has excellent touch support (think android etc). The support is built in manually and doesn’t come from some toolkit, thus you’ll see some behaviour differences between GTK3 apps and electron/chromium apps…”
That is the explanation I have seen so far. I thank-you.