8/30/2023 0 Comments Atom io vs coda 2![]() Small area, no information on cards, low information density, no zoom, no scroll. Timeline View is just not good enough to be useful. Overall the setup might work, but some views are quite weak. Epics and Features are connected together via a relation. In Coda I created a Product Tracking Document and two tables: Epics and Features. Epics are huge requirements that are broken 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) In Fibery there are less workarounds and everything is tight-knit together. You can build apps much faster in Fibery, but Fibery designed for internal productivity apps, while Coda works better for external apps and small team rituals. The vocabulary is as rich as in Coda, there are concepts like Space, Database, Field, View and Document. In Fibery you can create spaces with deep hierarchies, connect several processes together, extract information from several databases and replace sophisticated existing tools.įibery has pretty similar vocabulary: Space, Database, View, Document.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |