HN user

michihuber

53 karma

m -at- <my-username> .com

Posts2
Comments25
View on HN

Arc Studio – Remote

Looking for a senior Clojure/ClojureScript dev – need some experience with frontend ClojureScript SPAs. Ideally wants to build and manage a small team (but mostly build and write code).

We're building a git/GitHub for screenwriters. Documents with branch-and-merge, versioning, and real-time collab. What if Google Docs was built for deep collaboration in the first place, instead of being Word with some collab tacked on?

Apply here: https://tally.so/forms/w8rqOm

Also, distribution: Windows Defender requires code signing with an extended validation certificate, or going through the Windows Store. Otherwise users see a scary warning after installation how your app is probably a virus.

But using an EV cert means you cannot build on a CD service (it comes on a dongl). And users hate the Windows Store.

What am I missing as a mac person? I hear that most apps aren’t on the Windows Store. Is it normal to just have a virus warning and people ignore it anyway? Or can you just not distribute through a CD service?

I agree with this being about workflows, not documents, but isn't branching and merging a workflow and storytelling tool?

It allows multiple people to work in parallel (and in private). When somebody sends a pull-request eventually, they are presenting a story of changes that they want to get into the document and people can discuss them and approve them individually. (Of course, git the tool isn't necessarily suitable for non-technical people, but git-the-workflow seems to be a good foundation.)

Could you elaborate on what such a tool could look like without git style branching?

SEEKING FREELANCERS - remote - ongoing or one-off

  * ClojureScript frontend developer
  * UI/UX designer  
  * Quill.js expert
arcstudiopro.com is a collaborative screenwriting app written in ClojureScript (runs in the browser and Electron). There are lots of interesting problems to work on, from designing or building no-frills but user-friendly signup forms, to experimental onboarding UIs, or writing generative tests for our operational transforms offline support. The backend is written in Clojure, too.

Please also get in touch if you're familiar with quill.js internals.

work -at- arcstudiopro.com

Arc Studio Pro and Highland are very different.

Highland is macOS only and more of a minimal editor built around the fountain format (think markdown for screenplays), and has a very unique formatting UI.

Arc Studio Pro wants to support the full process and offers collaborative editing, automatic versioning, feedback management, outlining and visualization tools, etc.

Both apps offer a free version, so give them both a try.

It's true that the space is really crowded, but we also felt that all the other tools focused on formatting and not much else.

We wanted to consider the whole screenwriting process: collecting first ideas, outlining, distraction-free writing and formatting, collaborating, requesting and managing feedback, versioning...

Also, we want to take collaboration and versioning much much further than any existing tool and accommodate complex workflows, especially for larger writing teams. We're just getting started... :)

I've often had the same experience, people's workflows are pretty ingrained (in general, not just screenwriters). But I've done some pitches where a writer had a lightbulb moment, and realized that collab and versioning really would make things easier.

I put great emphasis on the app behaving similar to current screenwriting tools, and the collaboration/versioning features just being there when they are needed, so the change in somebody's workflow can happen gradually.

I'm curious which approach you had considered. And would love to get feedback from writers/filmmakers of all backgrounds: m@arcstudiopro.com

I thought it was great that screenwriters already had a notion of version control – once a screenplay goes into production, later revisions receive a color and are referred to as such, e.g. blue draft, pink draft. Pages that contained changes used to be printed on appropriately colored paper.

The idea of our app is to build on that notion and offer automatic versioning.

To everyone frustrated with notebooks, I urge you to check out nextjournal.com:

- Notebooks are automatically versioned

- You can reference and reuse parts of other notebooks immutably through something they call "Transclusions": https://nextjournal.com/nextjournal/transclusions

- The technology-stacks underlying each notebook are immutable, meaning that notebooks work on any machine (no "hidden" dependencies).

- You can explicitly reference other results instead of relying on global state, making execution order irrelevant.

It's currently in private beta, but people are starting to use it in production. (EDIT: You can sign up using the code curryon2018)

(Disclaimer: friends of mine are building this and I used to work on it in the past.)