Hacker News Reader

Comment by StanAngeloff | Hacker News Reader

My thoughts exactly. We've used GitLab since version 6 [1] and things have always felt like they are in a state of flux ([2] [3] [4]). For an open source project this is tolerable. I do wonder what enterprise users make of this constant UI change? Now that the navigation is back on the left, we'll probably see it collapsible in 9.5 and then morphed into a horizontal bar by version 10, rinse and repeat.

[1]: https://about.gitlab.com/images/6_0/mr_on_fork.png [2]: https://about.gitlab.com/images/8_0/ci_dash.png [3]: https://about.gitlab.com/images/9_0/navigation.png [4]: https://about.gitlab.com/images/blogimages/redesigning-gitla...

View on HN

As someone who has never used GitLab, it is perhaps interesting to note that I would have literally no idea of the chronology of those images you've linked; if I had to guess, I would say the grey one (1) looks older than the purple one (4), but the other two look almost entirely unrelated.

The images 1…4 are in chronological order, the URLs contain the version if interested. However, should you look at them in any order or sequence, it goes to show how different the UI has looked throughout the life of the product.

> For an open source project this is tolerable. I do wonder what enterprise users make of this constant UI change?

That's interesting to think about. What is the difference between the two types of users? Is it that the open source project is in no hurry and can accept a delay due to interface hassles? Is it that enterprise users are less capable and need a stable environment to function?

From my exposure to enterprise users, they are usually the sort of environment where hundreds, if not thousands, of employees work. Can you imagine how one "angry" of UI changes person in a team of a dozen scales set against that? With open-source users, it's more decentralised IMHO.

From my exposure to enterprise users their Gitlab updates will be wedged in the middle of a 2 year change control process and will jump over many iterations of design changes

If they were clever, they could structure the release schedule so that the enterprise customers which started with top navigation will renew when the top navigation is current again, and those who started with side navigation will renew when side navigation is on the mainline... ;).

When I read your questions, I immediately though: Enterprise users need processes. Processes goes by documentation. If you have to change your documentation once every 6 months because the blue button on the bottom left is now yellow on the top right...

Reply on news.ycombinator.com