Just for context, this is where I wish I could edi...
# infisical-feedbackf
Fernando Coelho
08/30/2025, 8:23 AMJust for context, this is where I wish I could edit the secrets, like it was before
v
Vlad (Infisical)
08/30/2025, 10:22 AMHi @Fernando Coelho! Let us look into this, and we will confirm in a bit 🙂
Vlad (Infisical)
08/30/2025, 10:22 AMcc @Scott (Infisical)
f
Fernando Coelho
08/30/2025, 11:44 AM@Vlad (Infisical) I don't mean to be harsh, I really like Infisical, but sometimes I just don't get why it is so hard to make a good UI for the secret editing page
Fernando Coelho
08/30/2025, 11:52 AMI wasted some time this morning with vercel v0 to actually show what I mean:
• Quick search
• Easy environment selection
• Easy environment compare
• Adding multiple secrets at once
❤️ 1
Fernando Coelho
08/30/2025, 11:54 AMHonestly I'm almost deploying this screen using infisical api 🤣
v
Vlad (Infisical)
08/30/2025, 12:00 PMOh wow! This is very comprehensive 😄
No, we really appreciate this. Let us sync up on this and we will follow up ASAP
🙌 1
t
Tony
08/30/2025, 12:31 PM@Fernando Coelho beyond being able to edit secrets while comparing across environments, I'm curious what your feedback is about the new experience of when you open up a project, it focuses on one specific environment with a separate compare environment modal as opposed to going straight to compare environments before.
If we add back the edit secrets while comparing environments, would this resolve most of your UX concerns?
f
Fernando Coelho
08/30/2025, 12:52 PM@Tony I think one or another is fine, as long as you can set which one you prefer. Someone who has lots of environments with different secrets on each one will benefit more from the new one. On the other hand, someone who is using a development -> preview -> production deployment flow (like me) will benefit more from the old one, since the three environments have equal structure but different values.
Fernando Coelho
08/30/2025, 1:03 PMAdding back the edit & compare table would solve most of UX concerns, yeah.
But you guys could also improve the new one, the new flow for adding a secret to all environments (dev, stg, prod) is:
Click "Add Secret" -> Type secret name -> Type secret value -> Click "Create Secret" -> Click "Save Changes" -> Type commit message -> Click "Save Changes" again
Then repeat this two more times.
I just ended up having to click 21 times and type in 9 times, that's because I can't perform changes on multiple environments and commit them all at once.
In the old one I'd just click two buttons, three dropdown items and type in 2 times.
Fixing this would improve the current flow a lot
t
Tony
08/30/2025, 3:13 PMGot it. Thanks for this feedback! I'll take this back to the team and see what we can do to improve 😄
c
Chris Gray
08/31/2025, 10:01 AMI tend to agree, we saw great value, specifically from an SDLC perspective of a straight up environmentSlug comparison right on the main section. Of course this was mostly when a new application is onboarding, thus working its way through the environments.
I do however see the new way being good once an app is established, and you just want to view env by env or update credentials accordingly.
v
Vlad (Infisical)
08/31/2025, 11:18 AMHi @Chris Gray! We will be releasing some updates in the next few days, and we will update you in this thread.
👍 1
Vlad (Infisical)
09/01/2025, 10:29 AMHi @Chris Gray @Fernando Coelho! We brought back the environment overview screen and will be releasing more improvements over the next few days 🙂
Thank you so much for sharing your feedback on this!
🙌 1
f
Fernando Coelho
09/01/2025, 10:40 AM@Vlad (Infisical) Thanks for the attention to feedback
Fernando Coelho
09/01/2025, 10:41 AMgonna launch a saas very soon, happy to have my comparing screen back 🥸
🚀 1