Showing posts with label UI change. Show all posts
Showing posts with label UI change. Show all posts

Monday, 19 September 2016

Prototype testing - invitation to the usability research

I'm happy to announce that we are ready to conduct a user research on a prototype of new Advanced REST Client.

List of changes is very long. Starting from general UI redesign to change in basic functionality.
The most important changes are:
  • new projects will support RAML (RESTful API Modeling Language) standard. Users will be able to import RAML file and use it as a "project". RAML contains API definition with the documentation that will be displayed alongside with the RAML request (new view in the app) and in project documentation page

Tuesday, 13 September 2016

Help us improve the app! - ARC prototype remote user testing

We are looking for people to participate in a usability test. We want to conduct research before actually starting and introducing changes to the app.

To qualify simply fill in the short form below. If you are selected, you will be contacted by a member of our team.

Tests will be finished in up to two weeks so there's no time to think about it. If you have 15 minutes just join the research.

Monday, 18 January 2016

ARC reborned

Hi developers,

For past 2 years I haven't been very productive developing the app. There was a lot of things going on in my life (work, study) and eventually I haven't got time to develop the app. Well, this is about to change.

For a last two months I moved the project forward. Source code is now available on GitHub and all issues has been moved there as well. I started working on app's improvements and there is a lot to do. So probably you'll be happy to hear that I'm developing the app full time now!

Tuesday, 12 January 2016

Encoding drop down removal from the app

Hi developers!


Update April 4, 2016
As of release 6 of the app the dropdown for content type header back to the app. Read more in this blog post.



I received a lot of questions about missing drop-down with predefined encoding values. I feel I owe you an explanation.

Lets begin of what it was. Encoding for payload is nothing more than value for Content-Type header. So when you selected one of predefined encodings (or rather mime types) the app added Content-Type header to the headers list before submission.

Earlier, the drop down list contained a list of predefined values for the Content-Type header. In fact this was only a shortcut for adding a header to the headers list. We all love shortcuts but..