From: Alyssa Ross <hi@alyssa.is>
To: "Vaida Plankytė" <vaidaplankyte@gmail.com>,
"Demi Marie Obenour" <demiobenour@gmail.com>
Cc: devel@spectrum-os.org
Subject: Re: UX: Initial use cases & actions
Date: Wed, 26 Aug 2026 16:10:30 +0200 [thread overview]
Message-ID: <87v78x7z1l.fsf@alyssa.is> (raw)
In-Reply-To: <CALi2N8TcPGRCvixtXOgRSNnz2_=GuCUbJ20GHOGOQRAtgoEdgA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
Vaida Plankytė <vaidaplankyte@gmail.com> writes:
> On Thu, Aug 6, 2026 at 3:50 AM Demi Marie Obenour <demiobenour@gmail.com> wrote:
>>
>> On 8/5/26 07:23, Vaida Plankytė wrote:
>> > On Thu, Jul 30, 2026 at 12:04 PM Alyssa Ross <hi@alyssa.is> wrote:
>> >>
>> >> * configuration? instance? I wish we had a better name for these things,
>> >> even if it's agreed that it's not necessarily what we end up calling
>> >> it to users.
>> >
>> > Agreed. I'm almost keen to just use "VM" internally because it's so
>> > much shorter to write, and explanations often end up mentioning the
>> > term as well as "persistent"/"non-persistent" several times a line, so
>> > it's a big space/cognitive saver. But maybe that says something about
>> > how user-facing terms, that'll appear in docs in potentially equally
>> > extensive explanations, should also be short and snappy. "Base app",
>> > "saved app" and "one-off app" or something.
>>
>> Qubes OS uses "Disposable VM". What about "Disposable app"?
>
> Disposable is a good word, as people are familiar with what it means
> from general life contexts. I quite like "app" too!
>
> Is "window" an option, or would it conflict with how people would use
> applications in Spectrum? If you choose to open a new window from an
> app's menubar, does it live in the same instance or not? I feel it'd
> be more natural for people to think of "app" to denote the actual
> application, and "window" to denote an instance/VM, as they're likely
> to be familiar with that terminology, but I can also see how that
> could get confusing if "generic window" and "Spectrum window" terms
> don't align.
Unfortunately that generally opens a new window in the same instance,
and that's not something we can change, because we'd have to change how
every app works. I definitely wouldn't want to overload "window" to
mean two different things!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2026-08-26 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 16:09 UX: Initial use cases & actions Vaida Plankytė
2026-07-30 11:04 ` Alyssa Ross
2026-08-05 11:23 ` Vaida Plankytė
2026-08-05 16:07 ` Alyssa Ross
2026-08-19 10:07 ` Vaida Plankytė
2026-08-27 8:40 ` Alyssa Ross
2026-08-06 2:49 ` Demi Marie Obenour
2026-08-07 16:12 ` Alyssa Ross
2026-08-19 10:24 ` Vaida Plankytė
2026-08-26 14:10 ` Alyssa Ross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v78x7z1l.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
--cc=vaidaplankyte@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).