Forum Discussion

msandoval's avatar
msandoval
Occasional Contributor
1 month ago

Change the UI style of ReadyAPi 4.0?

I just updated to 4.0, and the UI is horrendous. There's a lot of dead space. Is there a way to switch back to the previous UI without switching Ready API versions?

UI from 3.66

UI from 4.0

I already tried moving the bar down, but that's it doesn't go lower than that, so I'm stuck with that size, and I making my work slower since I have to scroll more than before

15 Replies

  • i Agree, the UI should be better to save visual space, and for my case i lost some data in my request, i did 3.67 rollback to continue working normally. i sent a email requesting support

  • Jeanette's avatar
    Jeanette
    Occasional Contributor

    I agree the new UI is not an improvement, it add space is a waste, and made it still worse for visibility issues, with lighter and smaller fonts, the extra scrolling and "pretty" changes reduces productivity and ease of use. 
    I have reverted back.

  • lynx's avatar
    lynx
    Occasional Contributor

    Oh my gosh, thank you msandoval​ for this .. I came here yesterday (I seem to have 4 accounts so my history is gone now) ..looking to see if I was losing my mind about the UI. So much waste space the request window (the most important aspect of the application is now barely visible .. I spend half my time now in the app scrolling up and down everywhere.
    Also, the grey font .. it is almost illegible .. i can barely read the headers. I was holding off on downgrading but everything took so much longer tocomplete today I will have to go back to 3.67

    a 1/3 of the screen is occupied where my yellow question mark is .. 

    • msandoval's avatar
      msandoval
      Occasional Contributor

      that's what happened to my, all that space lost, I didn't manage to work with it more than 5 minutes.   Honestly, I installed it, took the screenshots and uninstalled it.  Such a waste of time working with the new version.

      Let's see what they do the next release

  • Hi, thanks for your honest feedback. We updated the ReadyAPI UI in response to customer requests for a more modern experience and to align with the updated SmartBear design system, which also gives us a stronger foundation for improving accessibility going forward.

    We recognize that the 4.0 release introduces significant UI changes that may require an adjustment period for existing users, and that some areas may currently present usability issues or inconsistencies, including the ones reported here. We’ve documented the known issues and are actively addressing them. 

    https://support.smartbear.com/readyapi/docs/en/getting-started/welcome-to-readyapi-4-0-0/known-issues.html 

    A patch release is planned for next week to resolve the reported endpoint editing issue and additional UI concerns raised by customers.

    In the meantime, ReadyAPI 3.67.0 remains fully compatible, so teams can continue working without disruption while we roll out fixes and improvements. Download installers from the ReadyAPI Downloads Center.

    We appreciate the feedback and encourage you to continue sharing your experience — it’s helping us prioritize the updates that matter most. 

    • msandoval's avatar
      msandoval
      Occasional Contributor

      thomas_hurley​ thanks for the reply, honest question, who thought of making the most useful screen with the most important data on screen smaller? And, what does your other customer and smartbear think "modern experience is"?  This feels more like an ascii  based experience, I mean, look at this horrible design, it's just "v", ">" and "|" put together, if you were using a "└" to expand the objects, it would be less ugly



      This change just made the useless things bigger and the important ones smaller.

    • lynx's avatar
      lynx
      Occasional Contributor

      Thanks thomas_hurley​ .. useful to see the known issue page and SmartBear's plan to resolve some of the more 'abrasive' changes .. 

  • Hi everyone,

    We’ve rolled out a patch update for ReadyAPI (4.0.1) that addresses the issues reported in the editor related to spacing, the assertions panel, and endpoint editing.

    We’re also continuing to review the request/response editor panels and the Workspace Navigator for additional improvements based on your feedback. Those updates will be included in upcoming releases as we complete the work.

    We’ll also provide detailed documentation outlining the updates and changes so you can review them before upgrading.

    We appreciate your patience and continued feedback as we introduce these improvements.

    • bfields's avatar
      bfields
      New Contributor

      I have 4.0.1 this UI is still garbage.  I resized window panes to see info then tried to resize back and they will not resize back.  I closed app re-opened it it saved the sizing settings so now I am stuck with garbage app that I cannot see the things I need to see. Java is worst language for UI front-end development. It's great for backend but this is a garbage app now. if it was a piece of paper I would crumple it up and throw it away.

    • esoysal's avatar
      esoysal
      Occasional Contributor

      I upgraded to ReadyAPI 4.0.1
      In below screenshot;

      • I ran the test case in big red rectangle. All test steps passed.
      • Then I intentionally changed the last step's status code in the Assertion to make it Fail.
      • I ran the last test step individually. It failed as expected but didn't show as failed in the left-hand side. 

      • Have you removed the flexibility to test individual Test Steps thomas_hurley​ thomas_hurley​ ?  

       

      • esoysal's avatar
        esoysal
        Occasional Contributor

        New UI is awful, I agree all the comments here. But what I mentioned above is about functionality of the tool. Imagine you're building a test case with multiple test steps. Each test step is getting some values from the previous ones. You need to run the steps one by one to make sure each of them working as expected. 

        4.0.1 runs steps individually but doesn't show if it passes or fails. This is absolutely unacceptable. thomas_hurley​ 

  • gpatel's avatar
    gpatel
    Occasional Visitor

    Version 4.0.1 Looks even worse on MacOS.  Overall UI has very expanded look, including the fonts, context menus, the tabs, etc .. The bottom tab fonts way too big and so much valuable screen real estate is wasted in spacing / padding.    As it is the request/response panel editor was already small.  This update makes confines it even more.    For application that have large request and response body, Tiny view makes it very cumbersome to use the tool.

  • msandoval's avatar
    msandoval
    Occasional Contributor

    Skydivex​ had to do  the same, I rolled back to 3.67 and I'll be opening a support ticket for this, glad and sad to see I'm not the only one being impacted by this horrible change

  • 11111's avatar
    11111
    New Contributor

    Yeah this looks  like it was coded in Java Swing in  2005.