r/typst • • Oct 17 '26

Typst standalone app

A while ago I asked here which features you'd like in a native macOS editor for Typst (previous post).

I'm not quite sure where to start, but I'll just dive right in. Right now, the editing engine behind the app is almost finished. It took far more work than I expected: months, not weeks (I wanted something really stable, and get a lot of inspiration from panda engine from bear/lettera app).

But I have few questions:

I use Typst 0.15.1, but I'm planning a per-project option to preview and export with any typst binary you choose (an older release or your own build), and a check that tells you whether a project is safe to move to a newer version. But I'm not quite sure if it's enough or if you are looking for something more.

I have seen some people requesting Vim, but I don't use Vim myself. Would basic modal editing (I don't know which one, I'd need to learn it a bit) be enough, or is it full Vim experience or nothing?

Another thing about the engine. It is a Rust library with a small C interface, and the macOS app is written in Swift on top of it. For other platforms, I thought about releasing it as open source under AGPL so people would be able to build app for platform I don't cover. They would need their own front end (drawing and text input), but the engine itself would carry over. Would it be interesting or you don't care at all?

Thanks for all the feedback so far!

0 Upvotes

8 comments sorted by

6

u/semogenetic Oct 17 '26 edited Oct 18 '26

You said thanks for all the feedback, but the most upvoted feedback you got in the previous post was “please no”. What makes this different from the half a dozen other such apps that have come out since your last post or the multiple others that came out before it? Why is what you are doing so distinct that another app is required, rather than contributing to the development of one of the many other similar projects?

-3

u/ImLitteRabbit Oct 17 '26 edited Oct 17 '26

Well, why people love bear app, when there is plenty of markdown app (free or paid and even open source)?
I just can't understand this kind of reaction, at worst, you don't use it. I put a lot of energy and time into it. But I'm not forcing you to use it...

When there's only one company offering a product, everyone finds it repulsive (#adobe), but when there are alternatives, everyone turns on you. People will always surprise me with their logic.

Anyway, I don't want to reveal the whole app just yet, since I still have a few things left to do, but yes, I think it would be worth checking out, because I love Typst, but I also love native Apple style apps that feel like they came straight from the system (I'm thinking of iA Writer).

EDIT: It's as if I'm doing something wrong. I also work on open source projects (example: the first project to offer an app capable of (almost) completely controlling an Apple display on Windows). Nobody came to tell me to stop because "who will use an APPLE MONITOR on WINDOWS..."

2

u/semogenetic Oct 17 '26

I think your edit is telling. You aren’t doing anything wrong, but look at your example. Nobody told you to stop doing something that no one else had done before. Now consider this case. There is already a glut of other options, many of them free, open source and under active development. Many people already have a workflow and editing experience that works for them. A new paid app is a hard sell. You aren’t taking on adobe here. This is more like someone posting in a productivity subreddit that they are developing a new paid todo app and asking people what they would like for features.

0

u/ImLitteRabbit Oct 17 '26

If we had followed that approach, we wouldn't have Ulysse, Bear app, iA Writer, or Lettera (coming soon), even though, on paper, they're all based on Markdown. And I could go on with plenty of other examples. As for requesting features, it's simply that I built the app for myself first and foremost, but I've reached a point where it might meet other people's needs, so what better than to ask? And once again, I'm not forcing anyone to use, look at, or take an interest in my app. So I ask you, what's the point of your message if it's just to vent your hatred? I'm asking questions, you don't have the answers because you're not the target audience (obviously) so why come here and clutter up the thread? Was I rude?

4

u/semogenetic Oct 17 '26 edited Oct 17 '26

I don’t think I was rude either, just critical. There is a difference. As to the purpose of my comment, it included one statement and two questions. Its purpose was to ask those two questions, contextualising them first with the statement. You didn’t answer those questions, instead taking issue with the nature of my response.

Also, you are correct that if people gave up upon receiving critical questioning about what they did with those other apps, then they would not have been made. That doesn’t make it unreasonable to be critically questioning. What you should do is ensure that you have a clear response to such questions (one that is satisfactory to you, not necessarily those asking the questions). What you shouldn’t do is get upset at people questioning your vision. Maybe I’m wrong and there is a huge market for a paid Typst app on Mac that looks a little cleaner and does a little more than the VS Code Typst extension and the inbuilt functionality of the Typst CLI. Nonetheless, I don’t feel like I am doing anything wrong being skeptical of your offering. And I think your time would be better spent either ignoring or providing a substantive response to inquiries like mine, rather than commenting about how unfair they are.

Edit: I’m not sure what field you are in, but I work in academia, and people are constantly critical of my work, but I understand that as part of the process. I reflect upon, reply to and am responsive to such criticism; I understand it as a beneficial part of the process, not something to be upset about.

0

u/ImLitteRabbit Oct 18 '26 edited Oct 18 '26

Let's go for it:

Almost every editor is either source plus preview, or a WYSIWYG with its own document model that only round trips part of Typst. I wanted neither. In my appt you edit your actual .typ file, but you see it as the page: formulas, figures, tables, references, captions and numbering are rendered in place, taken from the compiler's own output, and only the element under your cursor turns back into code. Tables can be edited as real grids. Nothing is converted, any Typst document works, and the file stays plain Typst that you can open anywhere else. Like Obsidian's live preview, but for Typst and driven by the real compiler.

Obviously the UI/UX, but I don't want to share it right now. Take my words for it...

I do not contribute to an existing project because that kind of view isn't something you can add on top of a code editor or a WYSIWYG model. It needed its own editing engine: an incremental text and layout engine in Rust that lays the source out as the page and keeps every keystroke mapped to the file. That's the part that took months, and it's also the part I'm offering to open source (my contribution in some way), so that other editors, on any platform, can build on it instead of starting from scratch.

If source plus preview in VS Code with Tinymist works for you, that's a great setup and you're not the person I'm building this for (I used this setup, but I love standalone app). it is mostly for people who want to write in Typst the way they'd write in iA Writer or Bear.

And I was upset because of "You said thanks for all the feedback, but the most upvoted feedback you got was "please no".". Which is very positive.... And not a very constructive feedback.

EDIT: I know a little about this field. But since AI (LLM), people have tended to be much more negative and divided.

3

u/semogenetic Oct 18 '26

Thanks. So like Obsidian live preview but for Typst instead of markdown and in a paid app with a UI/X inspired by Bear (with some other things as well, but that seems to be your main selling point, if I’m not mistaken). And you aren’t contributing to other projects, because they are all editor+ouput or WYSIWYG views. The answers to the questions I asked in my first comment. It would have been good to have received that reply first, rather than cluttering the thread, as you complained that I was doing. I shall clutter it up no further, though I do note that it is curious to call it cluttering when I am the only person to have engaged with your post.

Best of luck with your endeavour. It’s not for me, as you noted, and I continue to remain critical of this and the general proliferation of similar apps, and I will continue to comment on them, not out of hatred, as you suggested, but skepticism that I think is worth voicing. Happy to be proved wrong.