you can’t refer other work items, mention people, create todo lists, etc.īasically, documents in Airtable do not exist.you can’t insert images into rich edit area.□ It’s really hard to create specifications in Airtable: This is how you supposed to work with it in Airtable: Usually it’s just a document with some images. Now I want to create a specification for an Epic. Navigating all views in Product Tracking space. □ All views are there, without limitations: These Databases are connected together via a relation. In Fibery I created a Product Tracker space with Epic and Feature Databases. Navigating all views in Product Tracking base. This breaks information density and makes Gantt chart useless.įeatures Roadmap quickly becomes unusable in Airtable. You see all features, even features that were completed a year ago. You can have it via Gantt Block, but it is just unusable. It has really bad information density and it is not possible to group work by rows.Īnother problem is a Features Roadmap. You can manage backlogs easily, do batch operations, group records by fields. Grid View in Airtable is close to perfection. I created a Kanban Board for Features, Features backlog as a grid, Features by People as a grid and even Features roadmap as a Gantt Chart Block (note, it is available only in the most expensive plan). Epics and Features are connected together via a relation. In Airtable I created a Product Tracking base and two tables: Epics and Features. Epics are huge requirements that break down to smaller requirements (Features).Īs a product gal, you want to write specifications, create product backlog, describe features, plan releases and track execution. Let’s take a simple Product Tracking process with Epics and Features. We’ll try to create a basic process in both tools. Translation sheet (as close as it can get) Fibery hasn’t found a good balance between freedom and complexity yet. In Fibery you can create apps with deep hierarchies, connect several processes together, extract information from several databases and replace sophisticated existing tools.Įntry barrier is higher. The vocabulary is much richer and you have to understand concepts like App, Database, Field, View and Document.įibery has pretty similar vocabulary: Space, Database, View, Document. You can’t really connect Bases (there is an Airtable Sync workaroudn that can work for some cases).To be honest, some blocks are quite cumbersome, but there are really cool blocks as well, like Page Designer. On top of that you can visualize data using several views: Kanban, Calendar, Grid and capture information via Forms.īlocks are extensions and you can add many blocks inside any base. Later you create another table and link them via relations, thus transforming basic spreadsheets into a relational database. The good thing is that you don’t have to think about initial setup, you can just create one table and work with it as with a spreadsheet. You create Bases (base usually dedicated to some process) and Tables inside Bases. Airtable started as an advanced spreadsheet and evolved into something more significant after that.Īirtable vocabulary: Base, Table, View, Record, Block. It’s easy to describe Airtable DNA with two words: spreadsheet and database. Philosophy Airtable is a set of connected Tables Let’s find out why.Īs the Fibery CEO, I have to switch off the bias. My goal is to explain how Fibery is different from Airtable and what strengths and weaknesses it has.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |