Wow, a milestone! Many features, like fullscreen and a dynamic sidebar 
, have been implemented. Thank you very much! 
However, I will wait with a full rollout until calculation fields are compatible with the new layout.
3 Likes
It is really nice to see development of this new layout 
. But like Roman said, we are using so much relations fields in almost every app, that we are still waiting to go full in.
3 Likes
We also use all the fields so we cannot switch a lot of items over BUT there are a few apps we were able to activate the new layout on. It’s so clean!
I love that we can build in the new, activate for only ourselves, and the permissions are all at the app level. This was strategic and smart 
3 Likes
Looks good!
But I hope that date fields will feature soon as well
1 Like
Just to clarify: existing date fields from classic apps don’t appear in the New Record Experience at all. Since dates are core to our workflow, this currently blocks us from using it.
1 Like
Hi @jon,
Really happy to hear that you like the new Record Experience 
We’re rolling this out step by step, field type by field type and only the field types that are already implemented are shown for now. So you’re absolutely right that the Date field isn’t supported yet
But I’ve got good news for you!
After we finish the Relation field, which is the biggest and most complex one, the Date field is next on our list.
Best regards
Leo
3 Likes
Maybe run voting as you’re deciding to what fields to prioritize. Might be a neat way to build some excitement and engagement in the community.
1 Like
Thanks for the clarification, Leo — much appreciated!
Good to know Date fields are next up after Relations. Looking forward to that 
1 Like
Hi Leo,
we also try to start production betas, but also feel blocked by missing field types. Afaik besides date also email, phone and owner fields are missing?
1 Like
Good morning @dirk_s,
Thanks a lot for sharing this. I totally understand the feeling of being blocked when certain field types are still missing. But no worries at all
The good news is that adding additional field types like email, phone or member will only take a fraction of the time compared to what we are currently investing in the Relation field.
The reason is that every field type is important and serves a specific use case. However, the Relation field is the key building block for many use cases at once. That is why we are going all in here and really want to deliver the best possible experience for our community.
Podio was already very strong when it came to relations, and we deliberately started there with the goal of taking it to the next level. We have incorporated years of Podio feedback and a lot of input from our community, including dynamic filters, new view types like list and dropdown, and many configuration options for how related records are displayed and linked.
Overall, we are on a very good path, and once the Relation field is solid, the remaining field types will follow in much shorter intervals. @1F2Ns based on actual usage patterns, customer requests, and development synergies, the next field types after relations are already largely defined. After relations, we will roll out Date first, followed by Number, which will then allow us to introduce the new Calculation field.
Really appreciate your patience and the close collaboration, and we are excited to get you into production betas soon🚀
Cheers,
Leo
5 Likes
Cool - the relationship field is already delicious 
3 Likes
relation field
Hey Leo – it looks like Relations might be wrapping up.
Does that mean Date fields are coming soon? Any rough timeframe?
1 Like
Hi @jon,
you’re absolutely right, as mentioned before, Date fields are next. We actually started working on them today
Right now, we estimate the development time to be a few weeks, not months. It’s always a bit tricky to give an exact timeline since unexpected challenges can come up, but overall it should be a pretty manageable timeframe.
I’ll keep you posted, and once we’re getting close to release, I’ll reach out again.
Best,
Leo
1 Like
Thanks for the update, Leo — really appreciate it! Great to hear it’s already in progress. Looking forward to trying it out
1 Like
@Leo and team, just chiming in with an additional feedback here regarding the burning need for date fields…
I realize you’ve already made it clear:
Our experience has been that Date fields are currently the #1 blocker for switching over in many app use cases.
A large number (like 80% or more) of apps require a critical date entry datapoint.
Task App 
Due Date
Project App Kickoff or Milestone Date(s)
HR/Team Tracker App Hired On Date
etc.
Even for several database app’s that are tied to forms. We will switch them to the old record style, add a date field, and add in some automations that auto-fill the date.
This then becomes available and visible in the table view even after we switch the app back to the new record layout.
We originally expected a high need for calculation fields, but honestly, new features are largely removing the need for many calc field use cases.
We do keep finding that having a Date and Number field option in the new record will allow us to make the full transition.
Excited to see those new field types soon!
2 Likes
Hi @jon,
we released the Date field today for the new Record Experience, Forms, and Mobile. So you can already use it fully with all the new features
I hope this unblocks your processes and that you can now move over to the new Record Experience.
Best regards
Leo
2 Likes