Old UI Was Better

[AbdelazizEl7or]

I still love and prefer the old UI 👌 The new UI's colors are so gloomy. It seems like it was designed 20 years ago 😁

[mike-ayres]

I thought the site got hacked. There was no real indication that it was going to switch, at least not one that I paid attention to. Normally I am asked to opt into a change. I agree with you on the look of it.

[ashishkjay]

OLD UI I WAAAAY BETTER!

[rtamarindo]

100% agreed

[AbdelazizEl7or]

It's better to roll back to the old interface, which was much easier.
Now, I'm immersed and lost in the new user interface.

[UtkarshYadav01]

Bring old UI back

[AbdelazizEl7or]

Bring the old UI back.

You can edit the old one to add some features instead of changing the whole design.

[keithdanielll]

I strongly agree!!!!!!!!!!!!!!

[viktaur]

Please bring back the old UI!!!

[iowjfiow]

a lot better

[anviod]

I agreed

[timofei-likharev]

I agreed, old UI was perfect

[lfox91]

The new UI is more functional, but I must agree with the others' sentiment; it's quite dreary. But hey, who said authentication should be fun?! (jk) You all put a lot of work and thought into the UI. Besides the color scheme and overall vibe, it's hard to find the new functionality. I visited the new page at least thrice before I noticed where the new JWT ENCODE link was. It took me a while- maybe two visits- to find the new claims table; you might want to make this the default, by the way. Finally, the example JWT is quite thin. This would be a great opportunity to teach new developers about JWT capabilities, thereby increasing your Auth0 conversions.

[detechlead]

Better yet. Kindly provide a way to switch back to the old UI for those who don't like the new UI.

[tonesandtones]

💯

The old UI was much better.

Some specific things about the old UI I liked that have disappeared from the new UI

• distinct colouring that make it obvious which parts of the decoded side map from which parts of the encoded side
  • New UI colouring is super subtle and barely noticeable, and decoded header/payload/sig sections aren't coloured to match the raw token parts.
• an "Algorithm" drop down to easily choose the algo, auto-populated from the encoded JWT if there is one
  • Does the new UI even support different algorithms? which ones? yes obviously it does, but it's not at all apparent as there is no drop down selector.
• claim name and value hover tooltips are much more pleasant to use. They look nicer and they're off the side a little instead of directly over top of the claim name or value.

One specific thing I like about the new UI,

• the two-pane layout isn't pushed all the way down 'below-the-fold' like it is on the old UI
• The claims table view is kinda neat, although the more usable tooltips on the old UI make it unnecessary

tl-dr - Go back to the old UI, collapse the page headers and branding to put the encoded and decoded panes front-and-center, and it'd be perfect.

[artfoor123]

old UI was perfect

[Kapitan-Morgan]

• please return old ui

[jestinjht]

Most people view jwt.io as a simple tool to decode and view a token. The most important word in that sentence is "simple". In other words, less is more, and new features should be resisted. It decodes a token, and even has the option of validating it. That is all it needs to do, and that is all it ever needs to do. Whoever suggested that it do more is wrong.

[ARahimKhan]

Older UI was better. New one is unintuitive and in cases where correct , exact standards are not adhered to (JWT secret size), it is unusable. Enforcing standards is not the responsibility of a decoder/encoder. It should work regardless

[ronaldroe]

What made the older UI better is its simplicity. It took me a minute to realize that to encode and decode are now separate states of the app. With the old UI, wherever I typed, it would generate everything else that I wasn't editing.

But if you do nothing else, please add the hover for the timestamps in the encoder.

[ccgetflag]

l like the oid version

[pavelezbob]

how to mutate the json, like in the old UI?

[SaifAqqad]

IMO the issue with the new UI is not the design itself (colors, etc) but the UX (weird behavior of the tooltips, separating the encoding/decoding to different tabs, etc)

[teja463]

This new interface looks very basic and ugly. Old interface is way better than this minimal UI.

[Lanny]

I'm hosting the old version for my own purposes here: https://jwt.lannysport.net/

If anyone wants to use it as well, feel free

[keithdanielll]

YESSS!

[AbdelazizEl7or]

Thanks, amazing !!!

[ghaliela]

How to switch to old UI on jwt.io

Just change ab-variant cookie to control

(new UI value is `variant`)

[advfromua]

Dude thanks very much!!

[AbdelazizEl7or]

This makes things better.

[TerenceEzreal]

Thank you~~

[anviod]

control

oKKKKKKKKKKKKKKKKKKKKK

[advfromua]

New UI made me angry on my IT day to day, because now I am unable to edit the payload it self despite the interface sucks.

[xixas]

new is ugly, hurt my eyes.

[TerenceEzreal]

For user convenience, a toggle button to alternate between the old and new versions would be beneficial

[eliezergwmnet]

please return old ui

[waqas-syed]

The new UI is not intuitive at all. I prefer the old UI.

Please provide a button to toggle to the old UI if someone wants to.

[ManuLpz4]

Old but gold, give it back!