I’m boring. The process for us was: Wifey and I thought of cool names, went to register with our shortlist written on paper, most didn’t work, until one did. Though now we’re considering dropping it because it costs too much.
I think you could play with sticky footers, sticky headers, and some active styling indicators like opacity and background plus highlights to let the user know they are in scroll mode. Really fun idea, love this! Wish Apple Music UI for moving songs on playlists had that. Holding my dumb while dragging is suboptimal comparing to click and scroll.
On your last point, could you elaborate? I have been using Next.js for a long time and I have never once interacted with Vercel. What soft lock-in are you referring to? I often deploy it using OpenNext and SST in AWS.
Curious to how much is just good marketing on their side and how much is maybe features of it I don’t know that are “vercel native”
If you are using OpenNext and SST (or Netlify), then you are doing it right. Most people assume you can just throw a Nextjs project into a docker container and don't realize that there are many features that don't just work "out of the box". The entire OpenNext project exists because of this massive gap
The reason I called it "soft" lock-in is because all of the nextjs features are technically self-hostable but often require extra setup that is sometimes completely undocumented. Until recently, Vercel itself didn't even use the default build outputs. It had an undocumented flag that skipped some serving logic that was handled by the Vercel platform itself.
Dax Raad from SST actually did an interview going more in depth into some of the features that don't exactly work "out of the box" as advertised (PPR, ISR, image optimization). This interview is about a year old and luckily Vercel has been collaborating with OpenNext to resolve a lot of these concerns but its still ridiculous that these were ever issues to begin with
I think this is the UX challenge of this era. How to design a piece of software that aids in promoting the human-level of attention to a distributed state without causing information loss or cognitive decline over many tasks. I agree that for any larger piece of work with significant scope the overhead of ingesting the context into your brain offsets the time saving costs you get from multitask promises.
My take on this is that the better these things get eventually we will be able to infer and quantify signals that provide high confidence scores for us to conduct a better review that requires a shorter decision path. This is akin to how compilers, parsers, linters, can give you some level of safety without strong guarantees but are often "good enough" to pass a smell test.
I really like this initiative, I think the biggest value here isn't the multiple sessions or worktrees, but an interoperable protocol between these coding agents through a new UX. A sort of parent process orchestrator of the many agents is something I want, is there other tools that do that today? e.g. run Claude, Codex, Gemini, all together and sharing data with one another?
Very interesting problem to even consider. That said, I don’t think we even understand the what, how, and why of music. The rhythm precognition aspect mentioned in another comment makes me think it’s just a byproduct of time and counting with pattern recognition, not necessarily a music thing just a correlation by virtue of physics and the laws of the universe.
/\__/\
(˶˃ᆺ˂˶) <(meow?)