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

[1F2Ns]

Most everyone here has a similar story. It feels like the Twilight Zone having a dev team who actively listens and asks for feedback. I’ve been here for a long while now and I can say that Tim, Leo, Stefan and the rest of the team are consistently making the platform better based on the community needs/wants.

[ScottA]

1 - would be great to have the ability to sign docs electronically and have an audit trail like HelloSign (now DropBox Sign) or any other equivalent. a lot of time is wasted currently generating the doc in Podio, downloading, dragging it over to the DB Sign and setting up evey single page with initials at the bottom for landlords and tenants to sign, then signature and dates at the bottom. We have to do that TWICE for every document as we don’t want to share the landlord’s email info with the tenant… so Tenant signs first, then we set the doc up a 2nd time for the landlord. Would be great to automate this.

2 - I logged this one as a bug, but maybe it should have been a feature request Shift to multi-select check boxes in table view - #3 by ScottA. …when in list view, would be great to being able to click a checkbox on the left hand side of a table of lots of items, then be able to go down multiple items, hold shift, and click another checkbox to check all the boxes in between the two checked ones. It’s a fast way to check 10, 20 or more items you want to edit/delete… vs checking each and every one separately. which is how it is now… and its painstakingly slow. See the image in the link above. We’re using Tape for all our inbound email… and sometimes you just need to delete 20 items in a single whack!

3 - the ability to open two items on one screen. Often times I am writing notes in one item, but need another item open to reference some information. When at my office I have multiple screens… but when traveling this is nearly impossible on a laptop. The other possible way to do this would be to give us the ability to close the activity/comments sidebar for more space, so we can open a 2nd item in a 2nd browser window and put the two items up side by side on the same screen.

4 - AND THIS IS A BIG ONE… A complete accounting package complete with ACH transactional ability for both inbound and outbound payments, reporting, etc. (I would love to put a bullet in our $ gouging QuickBooks bloat-ware!!!) I’ve thought this through… and its completely doable on your platform… It could also be another revenue stream as well for Tape for an accounting module add-on and a small fee for all inbound / outbound ACH transactions. I would KILL to have this feature baked into Tape and to finally have ALL our business operations in ONE platform. I’m available for questions… beta testing, etc.

Thanks - keep making Tape awesome… loving it!!

[R.J]

Hi all,
Let me please add an additional idea I thought I already included but I couldn’t find it now reading again.

SHOW/HIDE FIELDS FOR MOBILE/PC + CONDITIONAL
It would be very nice to be able to set shown or hidden fields depending on the viewport or on the device. This could be a “simple” latch option when configuring a field much like the ones we already have for hidden if empty or always hidden, but maybe like “hidden for mobile”. This would allow to show the information in a certain way in PC and/or mobile. In a similar way, a hidden in PC latch option could help to have some fields in mobile dedicated to directly enter information in Tape that are later hidden in PC. These could also be instead two latches show in PC and show in mobile.
Then if possible it would be awesome to “complicate it a bit more” by being able to conditionally show or hide in mobile and/or pc. This connects to some conditional logic in fields in general so this could replicate a show/hide fields based on conditions feature but based on the condition of using certain device.

By the way, for the 1st mention by @ScottA you could take a look at GitHub - OpenSignLabs/OpenSign: 🔥 The free & Open Source DocuSign alternative (checking the licenses) to have an starting point.

Thanks.
R.J.

[ScottA]

Thanks @R.J - I saw that in your comments above. That would be something I would need someone else to build… That’s above my head. But its great to know it exists if ever we go that route down the road. We’re not even migrated over to Tape yet… .just laying the ground work, getting to know the community etc. Thanks!

[R.J]

Hi @ScottA,
You’re very welcome! This “you could take a look at” was just a reference addressed to Tape’s team though. I wish you all the best for your transition. Thanks.

[1F2Ns]

I’m over here thinking about the conditional display for mobile view on fields.

This may be fairly straightforward using a user agent query.

You could have a toggle on all fields with the following options (default to both)
Display: [Mobile | Desktop | Both]

I can think of a few use cases for this, along with conditional logic as well.

[R.J]

Hi John,
Thanks for adding to this.

Sure, user agent could be used as well. For the toggle, I actually went with this “hidden route” since there are already some “hide toggles” in place. But both ways serve the purpose really, so nice also.

I believe there are many nice use cases for this. And adding conditional logic on top could be the cherry on the pie.

Thanks.
R.J.

[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!