I worry this is going to end up with a Cambrian explosion of tools that don’t interoperate with each other. This is the main side effect - anything that can be made into a business productivity app will be made into a business productivity app whether it makes sense or not.
For example - Facebook made itself into a productivity app, called Facebook at Work. It’s not great, but they use it. Notepad, Excel, literally anything that is a good ‘single-player’ experience will eventually end up one, either built by a third party, or if they’re smart and act fast, their own. It’s not a bad thing, it’s just probably better to let things shake down on their own for a while. We’re just now getting the social aspect of work right, after a decade of Google Plus grade attempts.
(Disclosure being, with some irony, is that I make a Reddit as an engineer productivity app at https://aether.app, so I have some personal experience with this proliferation.)
This “Cambrian explosion” is exactly what we’re trying to help with at Monolist (https://monolist.co).
The number of tools used daily is growing, which is in one way beneficial for the worker since they get a better and more specialized tool to do their work. However, it increases fragmentation and the chances of missed work.
Email is the most common solution, but that has its own downsides and seems to be used less and less for daily work. We think the solution is an ever-updating and fully synchronized “command center” for everything across every app you may be using.
I agree we need to attack this problem, but is another proprietary service to connect via proprietary APIs to your other proprietary services really the best answer? This looks like even more complexity than before (when something breaks, who do I go to for help?), except now I'm paying yet someone else to stand between me and my data.
We didn't get where we are today, in any field, using this approach. We don't have 30 different measurement systems, and a company whose job it is to coordinate conversions between them. We don't have 30 different text file encodings (any more!), and a company whose job it is to automatically convert them as necessary. We say: here's the standard, and now you can use it or be ostracized in the market.
If writing custom adapters to interface with GitHub/GitLab/Jira/... is anything other than a temporary solution, while you work on some grand plan to get issue-trackers all on the same page, then it's just a money-grab on the road to failure. Someone will cut off API access, or drive up your costs, or refuse to offer an API, and users will be stuck with "one command center (for the 3 most popular services they use), plus 3 oddballs", and it's just not going to be worth the hassle.
It's a band-aid. Normally you stick a band-aid on something that will heal itself, and then rip it off tomorrow. This particular problem is getting worse. This is a very pretty band-aid, but you've applied it to a sucking chest wound.
I think instead of another tool to wrangle too many tools is as you already headed off: email.
Gmail already reminds me of stuff like emails I didn't respond to. I've set up some filters and scripts to do more like create a triage queue for PRs and such.
Email does indeed catch and notify you of most things, and Gmail is getting smarter every day. The one major downfall, though, is that it's stale: the minute you receive an email it's out of date, and if anything requires additional emails to send updates.
It's also those "filters and scripts" you've set up to create your own triage queue that we're trying to replace. The average user should not have to write scripts to receive and process their work in an efficient manner. That's what we're trying to solve at Monolist!
That looks really cool, but unless employers are paying $10pcm seems steep to me, considering it's more than the underlying tools (which are potentially all used at free tier).
Have you considered pricing by #integrations connected?
We're always considering various pricing models, and per-integration was one of them. For the time being, though, we've decided that would be counter to our primary goal: allowing you to see and process all of your work from in Monolist, as quickly and easily as possible.
Yes, the problem is that all of these are not just programs but filesystems/databases. Nobody can be compatible with anybody else, except by drinking through the straw of an API, when you're allowed to. That means we're never going to settle on even bad ad-hoc standards like XLS.
The only standard that’s going to survive, I think, is email.
Anything accepts email - almost anything can send email. So for example in Aether Pro we’re building email pipelines so you can tie your CI to a ‘subreddit’ and all messages coming from that CI would appear under, without polluting everyone’s inboxes. It can also trigger further actions based on parsing those emails as well. It’s messy, but it’s the only thing that kind of works with anything.
We’d love to be able to rely on APIs of other tools, but those are just never there, or too fragile, or the API owners think the data they are ‘leaking’ is too valuable to let go, so email it is.
Funny you mention this. My friend runs a jewelry business and one of the things he needed to do was move something from Etsy to asana. There was no API so we used Zapier’s email parser to parse the order emails to send into Asana. Works pretty well.
That's interesting! Any yes, that's what we're going for, but in a way that also allows you to see the messages too, not just use as triggers. So you could bind your `support@` email to it and answer with humans as well.
It's all in the context of providing an internal gathering space that isn't just a notification-heavy Slack channel. Reddit-style forums work surprisingly well for both humans and robots, so it's pretty nice.
This is just a consequence of a free market. A communist would worry that letting people organize themselves to grow and sell food would end up with a Cambrian explosion of small businesses, each vying with each other for dominance. If they will follow the same model as everything else, we'll end up with monoliths in control of everything, just badly joined together.
> There’s an old joke that every Unix function became an internet company
Yes! I remember that. I worked at Sendmail at the time (a unix function that became an internet company) and we joked about starting a sister company called Syslog.
Given how many logging companies have sprung up since, maybe that wasn't such a bad idea!
I've been using Onshape and it's INCREDIBLE. It is a fully featured CAD package with assemblies, revision control, constraints etc. It makes Google SketchUp look like Notepad. I'm just using the free version (requires your files be public) but it's VERY much like SolidWorks. It's really an achievement in web app development.
I think one of the reasons for this explosion in new productivity tools we are seeing is the remarkable progress the web platform has made in recent years. I know web developers complain about the rapid speed web technologies are moving, but I personally am amazed by what's possible today. True, it's hard to keep up with everything, but I can't wait to see what will come out of WebComponents and WebAssembly.
Also putting all software in the browser doesn't necessary mean that the users have to give up control over their software and data. Maybe there's a middle ground by making it easy for the end users to run their own software in the browser. At least this is an idea I've been working on for quite some time - a self-hosted visual (no-code) software builder called FormBeaver[0] that let's users build and host their own custom database software without any code. Currently the users need to download it and run the App Builder on their own machine for it to work, but I'm hopeful that in the near future it would be possible to put it entirely in the browser thanks to WebAssembly. The one thing that's missing in the browser right now is an SQL database. I haven't found a way to run SQL in the browser.
Unfortunately, Web SQL Database has been deprecated in favour of IndexedDB, which in my opinion is no real replacement because it's a NoSQL database that's nowhere near as powerful in terms of the queries you can run with it.
However, the deprecation is understandable from a browser vendor's point of view. Maintaining and developing a browser is difficult enough as it is. Having to maintain an RDBMS adds a lot of complexity on top of that for what's probably a marginal use case for most users.
That said, it might be possible to integrate SQLite by using browser extensions. That of course depends on the users' willingness to install a browser extension in order to run your software builder.
I'm curious how the author's definition of "presentation software" might differ from mine:
> from a stand-alone PC application that saves files to a file share into a new collaboration-first web application. (I would really like someone to do this for presentations)
I consider that market fairly saturated: Google Slides, Prezi, slides.com...
I would like version control, tracking and sign-off per side, common central library (change this slide and it changes everywhere - good luck doing that with OLE)... I want workflow.
Using Slides etc is like moving from Excel to Sheets instead of moving to Everlaw or Salesforce - there's no change in the workflow. Slides is just a light-weight copy of Powerpoint, 'but on the web!'.
Not necessarily for presentations. We are working on a new work-sharing and communication platform for professionals that offers document versioning , tracking, workflow and e-signature (https://airsend.io/). From our customer development interviews we have found out that the "work context" is the most important thing.
Yes, 1) be irresistibly fun to use, 2) prevent users from doing the wrong thing, 3) be an aspirational purchase.
That might sound like I’m making fun of productivity software, but I’m not—-now that instant communication is a commodity, organizational/productivity software has value mostly because it’s a self-limiting tool that shapes how we think and interact so we can do what we were already capable of doing.
#2, and this comment in general, is a great point.
I recently wrote my first piece of productivity software, which I use everyday. The main benefit I get out of it is reminding myself, “This structure is how I want to think about things.”
The unlimited freedom of a spreadsheet comes with downsides, at least for me.
I keep a few emacs tables and template files for doing creative workflows. It’s easy to learn (once you bought into the eco system), fast to create (measured in minutes instead of hours or days), easy to use, and easy to modify.
The big downside to emacs for productivity is that it’s less easy to share.
Yes. This was (partially) foxpro. I'm building a relational lang (http://tablam.org - looking for help!) with the dream of turn it into an excel + access kind of thing.
Excel is great for ad-hoc exploration (is kind of a different repl!) but is best AT THE END of the data pipeline.
To make it well rounded, you need a good storage (rdbms), data language (sql, or hopefully my lang someday!), good way to do entry (CRUD form builder).
And at the end, put a spreadsheet and/or interactive repl like Jupiter.
More fancy stuff is welcome but this is the definition of a well rounded tool useful for small business.
IMO, make it realtime (i.e. Google Docs) and you have a great collaboration work flow.
----
My wife applied to residency last year. Each specialty has these giant spreadsheets (just like a database) they maintain collectively. which places are giving out interviews, how experiences were, what to look for, chat, questions, etc?
These are 20+ page spreadsheets. I briefly worked on an app for helping put this in a better format (spreadsheets suck on mobile). It's a ton of work just to match the basic functionality of this document.
I've worked in ediscovery software for years. Everlaw is definitely an up and coming player with an attractive interface, but no serious law firms/in house counsel have been using spreadsheets to conduct reviews for, oh, two decades at least
> There’s clearly a point in the life of any company where you should move from the list you made in a spreadsheet to the richer tools you can make in coolproductivityapp.io
Now there's a snazzy domain name (that, alas, was already taken).
Had to look up Monday.com. Watched the 5 minute overview on YouTube. Is it fair to say it's more or less like AirTable? Because that's what it looks like to an outsider. But Monday.com might have more integrations with other things that are common in the workplace.
We were evaluating Monday to replace Asana or Basecamp. It does a lot but the rough edges in the UI/UX really start to show once a team of size building a product starts to use it.
Slightly off topic, but there is some overlap between productivity and usability so some of you might be interested in my write up 10 important usability tools:
For example - Facebook made itself into a productivity app, called Facebook at Work. It’s not great, but they use it. Notepad, Excel, literally anything that is a good ‘single-player’ experience will eventually end up one, either built by a third party, or if they’re smart and act fast, their own. It’s not a bad thing, it’s just probably better to let things shake down on their own for a while. We’re just now getting the social aspect of work right, after a decade of Google Plus grade attempts.
(Disclosure being, with some irony, is that I make a Reddit as an engineer productivity app at https://aether.app, so I have some personal experience with this proliferation.)