rafBM

Amen to that. We reached $2M ARR as 3 engineers at Missive [1]. As the CTO, I can tell life wouldn’t quite be the same without the ability to save the day in the production console at the speed of light.

[1] https://missiveapp.com/

CTO @ Missive here, feel free to ask questions about our tech stack!

99.999% uptime is 5m 15s per year: https://uptime.is/99.999

CTO at Missive here. Thanks @pimterry for summing it up nicely. A note about the User-Agent: we do not forward it to the origin server as @mike-cardwell said. Our proxy always passes an iPhone User-Agent as a “lowest common denominator” to ensure CDNs won’t serve WebP images.

localStorage is no different than cookies from the perspective of privacy laws. https://softwareengineering.stackexchange.com/questions/2905...

We are using and customizing ProseMirror exhaustively at Missive (https://missiveapp.com/) Our rich text editor allows teams to collaboratively compose / review email drafts in real time.

In our first version, we used Firepad because it provided collaborative editing somewhat effortlessly. You can imagine how people have very strict requirements regarding email and old habits anchored in other apps (Gmail, Outlook, to name a few). Here’s the one thing we hadn’t thought that made Firepad a deal breaker: spell checking. Firepad’s rendering does not use `contenteditable`, which makes browser-native spell checking impossible to provide. Big bummer for many people.

We started searching for a contenteditable-based tool that supported collaborative editing. At the time, ProseMirror was the only candidate left after discarding Quill due to its overly simplistic document model (no nested lists nor multi-line quotes) and I believe this still holds true today. ProseMirror has actually come a long way to allow proper spell checking (see https://github.com/ProseMirror/prosemirror/issues/390). Marijn very kindly responded to feedback on this topic and ended up rewriting significant parts of ProseMirror to support it. I am extremely thankful for his dedication.

We are very satisfied with ProseMirror as part of our stack. I don’t think any other editor library offers all the options we need. Thanks a ton Marijn!

[…] all the GUI concessions that only webapps have to have. I don't know if users would ever accept this from a native desktop application […]

I bet you would be impressed by the GUI we have built for Missive - https://missiveapp.com/

It’s 100% web, yet it feels just as snappy as the best native clients. We also have a native macOS app that wraps the webview and provides a Dock icon, system notifications and Quick Look (space bar to view attachments).

We (founders of ConferenceBadge.com) never enjoyed Slack nor other chat apps because they encourage immediate attention, or you just end up missing out. And we are a team of 4… can’t imagine using it in larger organizations.

We never found any tool that would completely satisfy our collaboration needs, so we created Missive: https://missiveapp.com

It’s built on the idea that conversations should be scoped and archivable, just like emails. It’s both a full-featured email client and chat app. We can share emails and comment within threads, as well as create new chats from scratch and invite only the right people to discuss specific matters. When a topic is over, we just archive or snooze it like emails.

I have written in details about our vision: https://medium.com/missive-app/building-the-team-communicati...

Missive — https://missiveapp.com

Started as a collaborative email client, but expanding to offer chat and general team communication features. Your inbox already acts as a todo list, so it’s the best foundation to build a powerful and unified collaboration platform. We’ll ultimately become your one true todo list. One that gathers tasks from all channels: email, chat, etc. This pretty much makes us competitors to email clients, Slack, Basecamp, help desks, CRMs… name it. Big ambitions! ;)

Read more here: https://medium.com/missive-app/building-the-team-communicati...

Hi, author here. “Chat fatigue” posts are quite numerous these days, so this probably sounds familiar. But we do think our app - https://missiveapp.com/ - is a solid foundation for building a new kind of communication tool. It is pretty unique in its genre. Mixing email threads and scoped chats in one common list. What do you think?

Missive co-founder here (https://missiveapp.com). We built the app for a similar purpose: a way to share and comment around the heavy email load we get as a team.

Missive is designed to work with any email setup, not just shared inboxes. Our help@ and sales@ addresses just forward emails to our personal inboxes. This way each person keeps control of their own inbox, while being able to comment within threads and see who’s replying in realtime thanks to Missive.

Would love to have your thoughts. Feel free to ping me on Twitter @rafbm or rafael@missiveapp.com

Co-founder here, we indeed thought of crafting our tagline in such a way:

“With all these carefully thought collaborative features baked within an email client, Missive might very well replace your help desk, CRM, and messaging app.”

We do think there is a cost to always switch between multiple apps, but as new kids in a crowd full of big players, we’ve been wondering whether we should expect / try to catch users by “playing well with others” or be bolder and encourage them to ditch other apps?

Thanks very much for reporting this! It’s now fixed.

The numbers GitHub gives are a bit weird… here’s our output of `rake stats`: https://gist.github.com/rafBM/6837cc72f7958e2853ea

Thank you! Please report any bugs, that goes without saying… ;)

Awesome! Great UX. It is like http://duolingo.com or http://www.memrise.com for Poker. :)

These are all valid concerns.

It’s interesting that you’re not seeing the value in not having to code your own packaging/payment/update solution from scratch. From our point of view, this is the main value proposition in Gitiosk. We are not a marketplace, just a tool to make it dead easy to sell code.

We might be wrong about this. Let’s keep discussing! :)

— rafBM, one of the Gitiosk team member