# Terminology and App creation flows in ClickUp, Notion, Airtable and Coda **URL:** \ **Category:** Second Brain for Teams\ **Created:** [October 26, 2021, 7:19am UTC](https://community.fibery.io/t/terminology-and-app-creation-flows-in-clickup-notion-airtable-and-coda/2149 "2021-10-26T07:19:25Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 26, 2021, 7:19am UTC](https://community.fibery.io/t/terminology-and-app-creation-flows-in-clickup-notion-airtable-and-coda/2149/1 "2021-10-26T07:19:25Z")
This is a review of several major competitors in terms of conceptual structure (Apps, Types, Views, Pages). The problem with the new waves of no-code collaborative tools is lack of consistent terminology. | Fibery Term | ClickUp | Airtable | Notion | Coda | | --- | --- | --- | --- | --- | | App → Space | Space | Base | Page | Document | | Type → Database | List | Table | Database | Table | | Document → Page | Document | - | Page | Page | | View | View | View | View | View | | Field | Field | Field | Property | Column | | Relation | Relationship | Link | Relation | Lookup | View is a common term, Page/Document is quite OK as well, but other things are not unified and it makes everything more complex. We are in the evolutionary process here and terms should merge at some point. In Fibery we’ll do the following changes of terms: App → Space (Base is not clear, while Notion/Coda concepts are not applicable here) Type → Database (List and Table are close to Views, Database is not perfect also, but we have to choose the lest of both evils…) Document → Page (Page is more flexible and better suited for Block structure) ## Clickup The most complex of all. Notable things: - Space = App. - List = Type (user adds a list, which is a table in fact). User never deals with Type concept. - All Apps are visible in left menu, you can add folders inside. - Docs and Dashboards are separated into different menu categories. - Views are inside a List. ![ff85c8c3-a08d-4534-9a37-e945d3051a4a](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/abf4412d1c79c50b393ef3f668b575db393cb304.jpeg) New app creation flow ![d7a73585-d129-403f-be32-6fc069621ec3](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2eeb7a83cdb3837c629fda2d641f3014d2e21643.gif) ## Coda Similar to Notion in general. - Doc = App. - User deal with one Doc at a time. - Page = Document / Entity View in Fibery. Pages can be nested. - Table = Type (user adds a Table into a Page. He can select a new table or a view to existing Table). - View addition is equal to Table, you can create a new Type essentially or link View to existing Table (Type). ![76438055-a233-463f-ba29-a7e4246a2f4e](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a592eab5246d0be87ce297116d2c485c5584bdc4.jpeg) New Type creation flow. Note that you can create a new table or create a View in general. ![49897f66-4bec-46d8-81f1-fc7f8dc38751](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/bbd1eb9a22ce6e2b1ca2f0415f772b6b17303779.gif) ## Airtable - Base = App. - User focuses on one App at a time (as in Coda). - Table = Type (as usual, Type concept is hidden). - Views are inside Tables (Types). - Folders are available in Pro edition. ![49724467-0039-497c-a3d4-97380032ee7f](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a817696b137f3cd112e02c9b30fb3a91e020c523.jpeg) App creation flow ![9500e8f5-d1a0-45a6-a6c4-b02746389f01](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9281f8fd95edb3d7012f9e8e46332f330a324869.gif) ## Notion Similar to Coda. Page represents almost everything. In general there are only two abstractions in Notion: Page and Database. - Page = App. - Page = Doc/Entity View/Folder. - Database = Type (when you add Database, you ALWAYS create a new Type it seems). - Views are inside Database, but you can add ANY view to ANY page via a special / command “Create linked database”. ![35ce6f06-3a74-4269-85e2-20a13514df48](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/bc7d0635756f25842bc41b3b4b7d269d67c5fa48.jpeg) App creation flow ![ea1a811b-61ae-4fea-99b3-ccd3f28dc9ea](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2457bdc1f10b12d5b4277fd6199dba04b736b12a.gif) ## Observations - What about Type? - How many Apps I see at a time? - App creation flow: ## Concrete Fibery ideas - Re-design App creation flow in Fibery, remove meta-level and implement Airtable-like flow for App creation. - Embed Import into the app creation flow ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 26, 2021, 7:47pm UTC](https://community.fibery.io/t/terminology-and-app-creation-flows-in-clickup-notion-airtable-and-coda/2149/2 "2021-10-26T19:47:13Z")
This is good to see! I just want to note a lot of interesting and related discussion is happening regarding the choice of terminology, over here: > [@\[DONE\] clapper New Apps Creation flow, new getting started flow, new terms](https://community.fibery.io/t/in-dev-new-apps-creation-flow-new-getting-started-flow-new-terms/2148/2): > > Agreed. This looks more natural. I remember when I started diving into Fibery it was all very confusing even though I’m a dev. I stayed because I eventually figured out how everything works and was excited by the potential it has. “App” might not be the best naming as for me means something very dynamic and complex so I’m with you on changing the terms for both app and types. I remember i was confused by this term. I know from our own app, to keep the user coming back you have to give quick wi…