tablet

We'll definitely add mobile support in the future. It's hard to to everything with small team, so we have to focus.

Yeah, we'd like to focus on teams and companies more and provide a middle ground between flexibility of Notion and rigidness of Asana.

Our codebase is Clojure + Javascript

Why?

1. Fibery is not better that JIRA (or is better). JIRA is focused on software development, while Fibery can cover more areas and more processes. It really depends on your needs. For example, Fibery has no integration with source control yet. However, documents integrated with real work processes better than in JIRA.

2. Fibery is closed source.

3. We try to keep Fibery a broad product and so far we think our competitors are Notion, Coda and Airtable. Not Gitlab.

4. Yes, you can. Note that Fibery has no automations so far (only Zapier and API), it means some cases will be hard to have. Like email communication via Fibery with automatic linkage of all messages to some Account. You can check more info here https://help.fibery.io/en/collections/1831852-map-your-proce...

Let me know if any questions, we are ready to help with setup!

That was just an experiment. Now everything is real.

They are not random. If it's your first time at the website, you will see serious page and can see funny one after several deliberate updates (there is a special button for this). So if you just send fibery.io to a new person, he will see something serious for sure.

This will change soon. We were going to announce public release Dec 4th, but failed, as you see...

Well, some things take time. It is relatively easy to build something trivial fast, but it is not that easy to build something more complex. Markets are different. It took 4 years for Coda.io to release even private version. And they had like 50 people in a team. Our market is highly competitive and hard to enter.

Thanks! This is the most inspiring comment for a long time for us.

Hi, I'm Fibery Founder (and late to the party), so if you have specific questions, shoot.

You may create your own solutions and export/import them to new accounts, but we do not have any reselling program so far.

Fibery 1.0 focuses on creators. This is a person that:

1. Likely have quite specific problem domain (education, consulting, agency, etc.). In most cases such domains are not supported by mainstream tools well.

2. Loves to tinker with tools, build own solutions to the problems and play “power user” role inside his team.

3. Likes helping other people to solve problems.

It is not as easy as you think.

Take Slack.

Atlassian failed to compete with its Stride alternative and cooperated with Slack instead.

Microsoft Teams maybe a more viable alternative, but it's still less user friendly than Slack and it is remain to be seen who will win.

Money does not decide everything, you have to un-burden a department or run internal startup. This is hard and too few companies are doing it in a good way (Valve?).

The best way to validate a product idea is to build the product. And even that might not validate the idea itself due to poor execution.

The other surrogate (but faster) options:

- Build a web site and check traction/conversion rates

- Create a believable video from prototypes, show it to target customers and attentively watch face/eyes reactions (don't believe in compliments), look for phrases like "can I buy it?" or at least "can I use it now?"

- Learn how target customers work and try to build a mental mapping of your idea to their workflow. If you idea makes it significantly better (less tools, less time, etc), then maybe you have something real.

- Don't build MVP to validate the idea. They usually suck. In some cases they work, but only for a laser-sharp idea. If you have one, go for MVP.

In 20 years in soft. dev. industry I tried almost everything to improve estimates: delphi, planning poker, various formal techniques, points and estimation by compare, etc. Here are my rules.

1. In general I found that for rough estimate you can just multiply by 2 for a very experienced developer, by e (2.7...) for a developer with less domain expertise and by pi (~3) for an unexperienced developer.

2. If you need more precise estimates, then:

2a. do discuss every feature/story in depth, since it provides various opinions and help to find unexpected problems

2b. don't use points. Days are more reliable unit

2c. break down every feature to stories and every story to tasks. More granular items -> better estimates

That is it.

In-your-face ads are so annoying. How on earth someone upvoted this?

>I'm more curious about in what ways each application is better than what is currently on the market.

I think if you take best apps on the market Burnout will not be better. The power is in unification. How many features of Salesforce you use? Usually just 10-20%. How many features of Asana you use? Maybe 30-50%. And these applications have so much in common (Database + common UI + some integrations). You can generalize on that and still add specific depth for every app via extensions and power-ups.

Unification saves time and money. If you can run all these processes in a single workspace, you will always know where to find stuff, how to connect work with customers, don't have to learn new UI tricks with every new app and have clear picture of the whole business. I know it sounds too ambitious, but that is our goal.

Apps can be installed and uninstalled. If you don't need CRM, you will not have. Burnout can be simple or complex based on your needs.

Not. Here is the real screenshot https://d.pr/i/4yEClL

OK, proof https://d.pr/i/4yEClL

Hmm, indeed...

I personally dislike Monday. I traced its evolution and Monday valuation is totally insane, since product is a set of quite weird tools. They have good automations, but poor views and not very good connectivity between entities.

Notion, Coda and Airtable are more promising. But they don't focus on real work management (so far?)

Burnout strength is that you can install and connect apps together, thus creating a single workspace. For example, you have an Account in CRM. You can connect Account to Features, Invoices, Issues, Pains or Conversations, etc. It means you have a wholly connected domain that you can visualize and work with using Views (Table, Board, Calendar, Canvas, Timeline, etc).

Every App is created on a single platform (thus it is fast to create) and customized via PowerUps (UI extensions).

If you take Notion as an example, you can do pretty many things inside Notion and it competes with many tools as well.

You are taking this chart too seriously. Burndown, burnup, burnout...

Thanks, we wanted to create something "on the edge". But it seems quite many people take it as a satire. In the next version we will cool down a little bit.

It is more like GraphCMS [1] replacement. Basically you create required content structure (maybe Categories-Posts for blog or Articles for Help), write content inside our tool and publish via static generator somewhere (like GitHub/GitLab Pages).

[1] https://graphcms.com

Pricing plan (so far) is this:

- Free - up to 5 people (to help startup in the initial phase for free)

- Starter - $7/user/month

- Advanced - $17/user/month (automation rules, visual reports)

- Pro - $29/user/month (granular permissions, etc)

In general we can show what we have in private conversation. Pls fill in the form on a website and mark yourself somehow :) We will contact you.

No, this is not the case. We are working on the product for 3 years already and will release it in the next couple of months.