I hear a lot of teams have lots of different ways to manage simple repetitive tasks across the team, like Google docs, email lists, schedules and so on. So I built Firesub to try to simplify the work for teams.
For the last year or so I’ve been building a checklist management app for teams called Firesub.
The idea is to help make recurring tasks easy to remember and perform in a consistent way across the team.
It is an app that let you create and manage checklists that you and your team can follow whenever you need to perform a repetitive task like product development, code deployments, code reviews etc.
There is a ton of awesome features like assign people to checklists, scheduled checklists, email notifications when checklists is completed and so on, too much to write here, so please “check it” out. =)
-- Flowcharts
I think I need a bit more data on how users use the app and in what direction I should take the app and features before implementing this, but it's very possible I will in the future.
-- Conditionals
Yes, I'm thinking of adding something like this, but on a higher priority I will add Triggers, so a checklist can be started automatically based on for example, a time interval or a callback over HTTP.
I will also add Outcomes, so you can set up a action that should happen when a checklist is completed, like trigger another checklist.
-- Finder control over headers and items
I will work on this, with the goal of making as simple as possible to get started with the first checklist, but over time be able to use more advanced features for creating items.
-- Extended item details
Markdown is in the backlog. Alos item audit trail, like, Frej changed the description from ... to ... (5 min ago), and so on, so you have a complete track record of changes.
-- Merge items from "started-checklists" to parent checklist.
This is something I'm going to implement pretty soon, so that, when a person perform a checklist and discovers a the need of a new item, or an obsolete existing item, they should not need to make the change first on the active checklist and the same changes on the parent checklist.
-- On the roadmap for the near future
Triggers (se abow), Outcomes, Audit trails for checklists & items, "News feed" and Notifications center is things I have on the roadmap.
I'v just released a first private beta for a tool to manage reusable checklists like code-review checklists. For you HN readers, if you are interested you can try it out at https://app.firesub.com
The initial plan was to release a viedeo of the app, like Drew Houston did with Dropbox. But in my mind the video needed to be perfect, not showing any signs of bugs or misshaps, so I got a bit stuck with that. So instead I decided to go with a good landing page and screenshots insted. Thats way I thought it would be a lot of work in making a video demo.
That's true, I do not want to come across as a email gatherer. I have added a short description below the email input form for now, I need to go thru all wording to see how I can avoid confusion moving forward.
The current screenshots are the current development, I'v linked to a vide I recorded today as a way to clear up a the idea and workflow used in the app [0].
I will certainly fix the blog, I have no excuses for not updating it. =)
About the tag line, I am using "Reusable checklists for teams" or do you mean on the that I should remove the second heading on the landing page?
When it comes to your valid concern about the safety of pilots using a always-online application I agree with you, that would not be very smart, but nowadays there is technical soulutions around this problem [0]. Alsow it is a hint to everyone who have read the book "The checklist manifesto" by Atul Gawande, I recomend it!
I'v captured a screencast [0], literally a minute ago, of how app works, it's the worst quality ever but it showcases the idéa and the problem the app solves.
The very first prototype had a discovery feature where you could publish your own checklist under categories, much like the App store but within the app and for checklists. I decided early on that it would be a version 2 feature, because what good does it make to be able to easily find new checklists if completeing them is not "butter-smoth", another concern is of course that the "store" would be exceptionally empty in the beginning.
But the featuer is still in the "future features"-list.
I do not dissagree with you, the hacker news community is, of course used to play with new ideas showcased here, but after reading stuff from Eric Rise and Steve Blank and .co I decided to go after a "Minimal MVP" so to speak.
Hopefully no one is feling tricked by the title, if so, I'm sorry and beg your pardon.