🟢 Feature requests needed! Relaunching records, developing web forms, redesigning mobile

[1F2Ns]

Adding this here as well for consideration.

Would it be possible to save field names with the first save of the template? "copy_of_" Problem

I love the possibility to duplicate fields when building apps. Thats such a time saver. But as a Dev it hurts my feelings, when the external ID name is already given to the field before. a lot of “copy_of…” which has no meaning for the external field ID. I understand, that field names should be fix when created. But could they be given, when I save the new record layout the first time after I added the field? Currently the name is given when duplicating, without any chance to give it a meaning…

[1F2Ns]

I’m not sure if you have taken this to consideration yet or not, but it may be beneficial to have a UDF text block like we have on the new dashboards. This may be more intuitive for some users that are not as familiar with calculation fields. Just sharing because it crossed my mind.

[andrew.cranston]

I just had an idea, not sure if anyone else might find this useful or not. I know that soon (hopefully) fields will be sorted into sections, which may make this moot, but I was thinking about a particularly long vertical section, and to have the ability to “freeze” certain fields at the top. Even if there was one long single section page, if the “ID” of an item were the top row, and as the user scrolled down, that row would remain snapped to the top of the UI no matter what.

Just a random thought and I thought I would share! SUPER excited for mobile 2.0, I know so many people who are excited to move to Tape and are just waiting for it to drop.

[dirk_s]

We also need sticky first x columns for tables

[meetmaykel]

Hi @Leo I hope you’re having a great day. In case i missed it, is there’s any estimated timeline for the mobile version. I understand these things take time, but I’d appreciate any insights you can share.

Additionally, I was curious if the team is considering adding a dark mode option. The bright interface can be a bit straining during extended use, so it would be great to know if this feature is being explored.

Looking forward to any updates you may have. Thanks in advance for your time!

[Leo]

Hi @meetmaykel,

I’ve shared all the latest insights regarding our planned approach for a phased rollout strategy for the mobile version here:

Mobile App

Hi @ivica, @1F2Ns, @tomaz, and @andrew.cranston, First of all, a huge thank you for your kind words and creative ideas for the mobile app - we truly appreciate your input! We’re working hard to release the improved mobile app, forms, and new record as soon as possible. While we’ve made better progress than expected, the scope has expanded during development due to feature requests and foundational enhancements that needed to be considered early on, as they wouldn’t be feasible as add-ons later…

A dark mode is also planned, but it will come later in our roadmap, as we first need to develop all the features that are still blocking some users from migrating to Tape.

Best regards,
Leo

[R.J]

Just to keep this updated, here is a copy of what I shared here:

Mobile App

This is amazing to see the efforts towards mobile being pushed harder and harder! Just to add to the conversation, I wonder if some deep linking (android) or url schemes (ios) could help with @andrew.cranston #1: In this regard, maybe giving the user the ability to point a given link to the app or not depending on the workflow could be useful. Also as a side note, I really think that some copy of the desktop’s search functionality in mobile could be game changer. If this can’t be quickly imp…

1. Mobile search upgrade to make it similar to Desktop (or at least app filtering) could really improve things fast.
2. Conditional field visibility (already mentioned here but just restating the usefulness) to choose what to see when.

Thank you.

[dirk_s]

Its hard to keep an overview what has been said so far. I let some intelligence check and it seems like this was missing:

Conditional Field Visibility Based on User or Group

Allow fields (or entire sections/tabs) to be visible only to specific users or user groups/roles. This is especially important when developing new features or workflows that should not yet be exposed to all users. Example use cases:

• Show admin-only fields (e.g. internal notes, approval switches).
• Restrict visibility of experimental or under-development fields.
• Tailor views for different roles (e.g. sales vs. support).

Ideally, this should be configurable per field with conditions like:

• Visible only to users with role “Admin”
• Hidden unless current user is record creator
• Show only if user belongs to specific team/group

[dirk_s]

Here is the summary - i’m sure you have it done already as well

Feature Request Collection from Tape Community Thread

Records

Permissions & Visibility

• Add permissions to field groups and tabs (e.g., commissions, contracts).
• Control field visibility per view type (board, list, mobile, reference).
• Conditional visibility of fields/sections based on other field values.
• Conditional visibility of fields based on user, role or group (e.g., show admin-only fields, hide in-development fields from end users).
• Permissions at app, record, and field level; adjustable via automation.

Field Behavior

• Lock fields so only automation can update them.
• Freeze calculated fields after certain conditions (e.g., when status = “completed”).
• Support for today() function in calculations.
• API responses should return fields in fixed order and include empty fields.

Other Record Features

• Merge duplicate records with auto-updating of all linked references.
• Filter records based on the number of incoming links.
• Display linked records as editable mini-canvases.
• Advanced layout options: collapsible sections, split view, tabs, pop-outs.
• Ability to hide apps from the main interface.

---

Web Forms

Form Capabilities

• Allow multiple form variants per app with different layouts/fields.
• Pre-fill forms with values from linked records.
• Conditional visibility of fields/sections inside forms.
• Custom labels for fields (e.g., using questions instead of field names).
• Show/hide calculated or hidden fields in the form.
• Read-only fields inside the form.
• Group fields into sections.
• Multi-page forms with progress bar.
• Auto-save for long forms.
• Display confirmation messages or redirect after submission.
• Conditional logic upon submission (e.g., different outcomes based on input).
• Support for nested data from linked apps.
• Signature field (including support for e-signatures).
• Custom form design via CSS.
• Embed forms in external websites.

---

Mobile

Views & Navigation

• Create/view records without entering edit mode.
• Custom “mobile view” with selected fields only.
• Add the “Focus” view as a tab in the mobile app.
• Add custom dashboards as mobile tabs.

Interaction & Automation

• Support for buttons triggering automations.
• Click-to-call functionality for phone number fields.
• Take/upload photo outside the comment section.
• Improved notifications with action buttons, file previews, or links.
• Better mobile-optimized notification experience.

---

Technical & API Features

API & Data Structure

• Fixed field order and completeness in API responses (even for null values).

Automation & Templates

• Support for templates in automations.
• Generate DOCX or TXT files automatically.
• Integration with open-source tools for e-signatures.

PDF Generation

• Overlay text and images in PDFs.
• Control margins and page orientation.
• Add map visuals (e.g., Google Maps) in generated PDFs.

---

Security & External Access

Access Control

• Password-protect shared fields or files.
• Expiring public share links.
• Log access history for shared content.

External User Portals

• Lightweight customer portals for file upload.
• Partial submission support (users don’t need to fill out everything at once).

[andrew.cranston]

Great summary, @dirk_s !

@Leo @Tim Now that we are officially out of Q1 2025, is there any roadmap update on any of the things that were planned to be launched by Q1 end? Should the roadmap be updated to reflect the updated timelines? I’ve been pointing a lot of my clients to the roadmap so was just expecting it to be updated with the most recently available information.

[dirk_s]

I forgot to mention - the kudos go to ChatGPT. Someone had to do it.

[dirk_s]

There seems to be missing this one:

Show the names of the linked apps with the linked field in a calculation field. There is currently no way to find out, which app is linked. Field names are not unique. So the linked app needs to be easily recognisable with the linked field.

Thats a pretty tough job, if you want to analyse existing code in calculation fields currently.

[Nele_Claeys]

Just like @andrew.cranston points out, it would be very helpful for me to have an idea of the timeline for releasing new developments (especially the webforms in my case). As it has implications for projects I’m currently designing… Thanks!

[Leo]

Hi @andrew.cranston and @Nele_Claeys,

We recently updated our roadmap, thanks again for your note @andrew.cranston. You were absolutely right, the timeline needed an update!

There are still a few basic building blocks we’re working on, where we’re using some new technology. This makes it a bit hard to give an exact timeline right now. However, we’ve already finished many features that are currently held back because they depend on other parts still in progress. In the roadmap, we’ve marked these as “Ready – Blocked” so it’s clear what’s done but not yet ready to ship.

We’re not just building web forms on top of the current system. Instead, we’re rebuilding the whole app and field creation process to match what our community needs, now and in the future. That’s why we’re also working on several important features that will help create a better experience overall and avoid rework later.

A good example is field-level access. A feature many of you have asked for. It’s already completed but currently still blocked by other dependencies. Once released, it will make it easy to control who can see or edit specific fields. Since this works directly on the field level, it doesn’t just affect forms, but also records and views throughout Tape. That’s why it needs to be built into the system upgrade from the start.

We’re working hard to deliver the first version to you as soon as possible. Once that’s in place, we’ll be able to move quickly and build out many of the requests and ideas you’ve shared. Thanks again @dirk_s for collecting all those suggestions — they’re incredibly helpful!

Wishing you a great evening,
Leo

[andrew.cranston]

@Leo SO EXCITING!!! Thank you guys so much for all your hard work!

[1F2Ns]

Man, reading the roadmap makes me so damn excited. You know you’re on to something when your customers are celebrating features that haven’t even been released yet. This company is amazing!

[Leo]

Sneak Peek: Forms

Many of you have been waiting for a preview - and we totally get it, because it’s already starting to feel really good.

Today, we’re excited to share a video showing the latest progress.
Some examples:

• Form creation process - it’s super easy to create new forms - and it already feels really smooth
• Rename field – instant, inline renaming of fields without leaving context
• Mass changes – e.g., set multiple fields to “required” across multiple fields at once
• Edit style – update field styles, label positions, or placeholders
• Dynamic columns – add, remove, and reorder columns
• Rules – enabling conditional logic like showing/hiding fields based on input
• Field access – define field-level access to control visibility

The same technology will also power the new record experience.
(Please note: some details may still change as we are currently running lots of tests)

As you can see, a lot is already coming together, but there’s still a lot on our roadmap before the launch is complete, as I mentioned a few days ago → here

Anyway, we’re officially opening the waitlist for Forms today.
We’d like to invite you to get early access → https://get.tapeapp.com/forms/

Thank you so much for your ongoing support and patience. We’re super excited for what’s coming! Whenever we hit another good milestone, we’ll share another video with you.

[DigiTom]

Wow, this looks insanely promising! Can’t wait to get my hands on it!

[dirk_s]

Great sneak preview, @Leo … can’t wait to get access and introduce it into our clients environments.

Could you also say, which fields types will be supported? Will there be file uploads or will they be added later?

[R.J]

This seems amazing!!!

Please don’t forget the mobile record search upgrade (much like pc). Thanks @Dirk for your summary (it appears to be missing the mobile search revamp though).

Thanks a lot.