Home
Qatalyst
Home
Qatalyst
Getting Started
Study creation & Analytics
Question Blocks
UX Blocks
Qatalyst Features
User Management
Roles & Permissions in QatalystAccess User ProfileView User ListChange Roles of Users
Release Notes
November 8th, 2024October 23rd, 2024October 8th, 2024October 4th, 2024October 1st, 2024September 27th, 2024September 24th, 2024September 23rd, 2024September 19th, 2024September 12th, 2024August 30th, 2024August 22nd , 2024August 14th , 2024August 8th, 2024July 24th, 2024July 17th, 2024July 10th, 2024June 28th, 2024June 20th, 2024June 18th, 2024May 31st, 2024May 27th, 2024May 23rd, 2024May 14th, 2024April 23rd, 2024March 28th, 2024March 19th, 2024March 6th, 2024March 6th, 2024February 29th, 2024February 16th, 2024February 14th, 2024February 8th, 2024 February 01st, 2024January 31st, 2024January 24th, 2024January 11th, 2024December 29th, 2023December 20th, 2023December 14th , 2023December 6th, 2023November 22nd, 2023November 20th, 2023November 6th, 2023October 27th, 2023October 18th, 2023October 9th, 2023September 22nd, 2023September 15th, 2023September 8th, 2023September 6th, 2023August 31st, 2023August 24th, 2023August 21st, 2023August 19th, 2023August 2nd, 2023Release Notes - July 27, 2023Release Notes - 17th July, 2023Release Notes - July 11th, 2023Release Notes - July 4th, 2023Release Notes - June 21st, 2023Release Notes - April 20th, 2023Release Notes - June 9th, 2023Release Notes - June 7th, 2023Release Notes - June 5th, 2023Relase Notes - May 26th, 2023Release Notes - 22nd May, 2023Release Notes - May 19th, 2023Release Notes - May 12th, 2023Release Notes - May 5th, 2023Release Notes - April 28th, 2023Release Notes - 18 February, 2023Release Notes - July 19th, 2023Release Notes - April 7th, 2023Release Notes - March 30, 2023Release Notes - March 28, 2023Release Notes - March 23, 2023Release Notes - March 21, 202317 March, 202304 March, 2023

Release Notes - April 28th, 2023

What's New?✨

  • Prototype Testing: We are excited to announce the latest addition to our UX research platform - Prototype Testing! With this new feature, you can now test the usability and functionality of your designs. To get started with prototype testing, you will need a Figma file with at least two screens. Please note that for now, we only support Figma files. Also, the file should hold only one set of screens. Once you have uploaded your Figma file to our platform, you can easily create a prototype test. Our platform allows you to track and analyze user behaviour, identify pain points, and make data-driven decisions to improve your design.

Under the prototype testing, we have added the following two journey types:

Defined Path: Defined path is a predetermined sequence of steps or actions that a user can follow to complete a specific task or goal within the prototype. However, Qatalyst allows you to define multiple paths for the different screens. The end screen will be the same, and the user can change the start screen of the test. In between the end and start screen user can define multiple paths.

Exploratory Path: In this path type, while creating the research, the user can define the start and end screen, and while taking the test, the respondents navigate from different screens to reach the endpoint. Using this technique you can identify if participants can finish an activity effectively, the time needed to accomplish a task, adjustments necessary to increase user performance and happiness and examine the performance to determine if it satisfies your usability goal.

  • User Profile Page: We have added the User profile page. Now, users can view their profiles and make changes to their personal information. The User Profile Page displays all essential details, including First Name, Last Name, Mail ID, Roles, Job Function, and Display Picture.
  • Now users can view other users' profiles on our platform. Owners, Admins, and Editors with view access can easily view and edit other users' profiles. The Other User's Profile Page contains all necessary details, including Name, Mail ID, Roles etc. However, some fields like Display Picture, First Name, Last Name, Mail ID, Country, and Time Zone are non-editable and cannot be changed by anyone. Owners and Admins have an additional button on the Other User's Profile Page - Deactivate or Activate. This button allows them to deactivate or activate the selected user's account. 
  • Technologies: Added functionality, using users can easily configure their studies with specific technologies like mouse tracking, eye technology, and a combination of facial coding + eye tracking. With this, users can now select the technologies they want to use in their studies, which will allow them to collect more detailed and precise data. 

  • Mouse Tracking Technology: When a user creates a study with UX Blocks and enables Mouse Tracking Technology, they can click on Preview or publish the study and use the shareable link. The tester's mouse-related activities will be traced during the study, which will be later used in the insights part for the respective blocks.
  • Eye Tracking Technology: We have configured the tester view when testers are taking tests with Eye tracking technology enabled. The device permission is asked first for enabling the camera, and the user is then asked to take a calibration test.
  • Added functionality which will enable the users with the role "Editor", will be able to view the user profile and settings page. Editors can only view the user profile but cannot open other user's profile and edit it.
  • We have updated the results page of A/B or preference tests. In this update, we have introduced a new bar graph component that visually represents the percentage of users selecting each image. The new bar graph component enhances the visualization of the results, making it easier to understand and interpret the data.

Bug Fixes🔧

  • Fixed a bug that caused the preview icon and properties of a block to appear in a disabled state until a refresh was done. With this fix, the preview icon and properties will now be immediately enabled after the mandatory fields are added to the block.
  • This bug fix addresses an issue where toggling on properties from the right pane would pass mandatory fields as empty in the payload, resulting in the status of the study remaining as draft and preventing the user from being able to publish or preview the study. With this fix, mandatory fields will be properly populated in the payload when properties are toggled on, ensuring that the study can be published and previewed as intended. 
  • Fixed a bug that caused an incorrect error message to be displayed when a user attempted to upload a large prototype file for a prototype block. Previously, when the import file took more than 55 seconds, the upload would fail with a 504 error, and the user would be displayed with a "Something went wrong" message. With this fix, the user will be displayed a more accurate "Network Error" message
Powered by Product Fruits