Frontly buying guide: reusing a card design is not the same as showing one card per record
Use a fictional equipment lending page to distinguish one shared notice from status cards driven by records.
Frontly's April 2025 help documentation explains reusable and repeatable blocks separately. Reusable blocks use an existing design in different places. Repeatable blocks can connect to a data source and show a value for each record. This establishes the difference, not that every interface in the older guide looks the same today.
Count how often each kind of information should appear
Imagine a fictional equipment lending page. The top needs one “Return equipment to its original rack after use” notice. Below, three items each have a name and availability status. Putting the notice inside the repeated cards makes it appear three times and disappear with zero records. Copying availability as fixed reusable text makes three statuses look like the same record. Keep the shared notice separate from the card for each item.
On paper, test records with 0, 1, and 3 items. The notice count stays fixed; the card count changes with the records. Test an empty status separately: the placeholder should say “needs verification,” not copy the previous item. This checks a design rule, not whether Frontly automatically handles blanks a particular way.
When is a static table enough?
If several pages share a notice and item counts often change, compare this division of blocks. With a few stable items, a static table is simpler to inspect by hand. Include the time needed to add images when adding records, review missing values and revisit the shared notice. This comparison uses original paper cards; it does not connect data, operate an app or test permissions.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:help.frontly.ai