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.
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!
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.
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.
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.
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.
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!
Iāve shared all the latest insights regarding our planned approach for a phased rollout strategy for the mobile version here:
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.
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:
@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.
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.
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!
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!
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.
Feature Request Collection from Tape Community Thread
Records
Web Forms
Mobile
Technical & API Features
Security & External Access