Solved

Can I replicate database views in Lucidspark?

Forum|Forum|1 year ago
August 14, 2025
4 replies
76 views

Hello.

Every major app has “views” from Notion to Coda to Airtable to Trello…
Can you replicate them in Lucidspark with the Lucid cards?
How many views can you achieve?
How well can you switch from one to the other without the typical tabs to switch views?
How seamlessly can the Lucid cards move from one Lucidspark view to another?

Thank you for your time. Bye.

Best answer by Zuzia S

Hi @patrickpereira1988, thanks for your post! Lucid doesn’t currently support a native “views” feature as described. As a workaround, you can use Lucid Cards to represent items, then arrange them manually into grids, lists, or sections to mimic different views (though these are static, not automatically filtered).

It seems like a very a similar idea has been brought up in our Community in this thread:

Dynamic table, regular table....database table next?

If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within that thread. For more information on how Lucid manages feedback via this community, take a look at this post.

Cheers!

P

patrickpereira1988Author

P

patrickpereira1988Author

Was able to replicate four of them.

P

patrickpereira1988Author

Even though there is a dynamic table and regular table feature in Lucidspark neither one functions like the ones found in Notion, Coda, Airtable, Walling. Craft or Xtiles.
Example below from Notion.

In Lucidspark the Lucid card title would be the first column. Description the second column. Assignee the third column. Status the fourth column...

Zuzia SAnswer

Lucid community team

Hi @patrickpereira1988, thanks for your post! Lucid doesn’t currently support a native “views” feature as described. As a workaround, you can use Lucid Cards to represent items, then arrange them manually into grids, lists, or sections to mimic different views (though these are static, not automatically filtered).

It seems like a very a similar idea has been brought up in our Community in this thread:

Dynamic table, regular table....database table next?

If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within that thread. For more information on how Lucid manages feedback via this community, take a look at this post.

Cheers!

Create an account in the community

Log in to the community