![]() ![]() Familiar interface can certainly be comforting for some users, but we firmly believe that a visually pleasing and intuitive interface plays an important role in usability and acceptance of a software. Very little has changed with regard to layout and design over the past decade. ![]() Redmine it seems has prioritized technical development over user interface and design. Also, this required the development of the new REST API v.3. ![]() creating work packages directly in the list view. It allowed us to improve the usability significantly, e.g. After a detailed feasibility study and numerous prototypes we decided to integrate the popular JavaScript framework Angular. Using our own software every day it was clear for us that we wanted to move more towards a single-page application. Most actions require an entire reload of the page (e.g., updating a work package/issue). Redmine is a traditional Ruby on Rails technology stack. Let’s take a closer look at how both tools evolved over time. It is indeed surprising that people are still drawn to it despite the very outdated design and usability that seems to be stuck in time. Redmine has been around for over a decade, yet it remains quite popular. It has been well over 10 years since we forked in 2011, a lot has changed, many new features and improvements have been added to OpenProject. We wanted to have a tool every project member is happy to use - not only tech-savvy users. And this reaction makes us quite proud, since this means we made significant progress with our goal to build the most user-friendly open source project management software. We often get a surprised reaction when people hear this. You may not know this, but OpenProject is a fork of Redmine. Redmine: A comparison of OpenProject to Redmine shows how both tools now differ in design and usability even though they have the same roots. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |