It seems like no one can defy the change towards "flat-design" in modern software. Don't get me wrong, I like it for the most part.
But who actually designed the new SourceTree UI, stepped back, took a deep breath and thought "Yeah that looks good"?
The UI had lots of changes in the past and most of them made it worse in terms of usability and readability, which is a pitty. The lack of contrast and outlines makes it a total mess for me.
I'd like to start by acknowledging that we should have done better in communicating our intentions and how we are resolving concerns around this very passionate topic.
As noted previously in thread, the substantial UX redesign was first introduced nearly two years ago for both platforms with additional changes as necessary. One of the goals was and is the fidelity of Sourcetree between platforms as well as with the rest of the Atlassian family. And in an effort to tackle the very common complaint of interface bloat, we also removed several buttons from the toolbar and other areas that were either redundant or infrequently used.
Since this admittedly rocky start we've listened to your feedback and made some changes:
One of the most contentious aspects was the removal of the treeview (sidebar) from Sourcetree for Windows. Jens, our Head of Product, recently posted an official response in SRCTREEWIN-7176 to help move us all forward.
Thank you for your patience and feedback around the pain points you’ve experienced with the UX changes. We do strive to improve the experience overall for the wide variety of users in our community but don't want to strip away everything you've come to know and love. We have work to do internally to better communicate and listen and I hope you can help us by staying positive and encouraging!
Product Manager, Sourcetree
I literally reverted back within 10 minutes because the new version is an unusable mess from a design perspective.
The new design suffers from a serious lack of understanding for the purpose of the tool or its functionality. It is as if a bunch of designers, who have little to no understanding as to the use of the tool and its design choices, were placed in a room and told to peck away at the UI design until all the elements conformed to an arbitrary flat "design vision"; and that these changes occurred in a vaccuum without an understanding of how those changes impact programmers or build engineers who actually use the tool on a regular basis.
This is just a suggestion, but if you want to make design changes to a programming productivity tool, you should actually consult programmers who use the tools regularly for their input.
Atlassian & @Mike Corsaro, responding to the only positive responses, when the bulk of the responses is negative, is lip service. You guys need to seriously rethink how you're handling the PR of this. If people are upset, ignoring the pleas for sensibility is a sure fire way to upset your users more. You guys are a lot better than this with all of your other products, so this is really disappointing to see coming from a company with otherwise great tools.
Totally agree. The first versions of Sourcetree showed deep understanding of git and its use. the last few versions showed a total lack of understanding. Just a few designers moving buttons around and changing colors. I am sure the new bugs will eventually get worked out but the damage that has been done to a formerly very productive tool will be hard to get undone.
I reverted back in about 2 mins... as it no longer saw any of my repositories... when I tried to open one from the bookmarks.. it said it was not found and asked if I wanted to remove from bookmarks. When I looked on the filesystem it was still there... I reverted back to 1.7 and hey presto everything worked again.....
It was a great product... I really hope they just roll it back to 1.7 and then start beta testing new releases.
I don't think they will. ST is now a free product, what means that YOU are the real product.
So now they need to expand the user base at any costs in order get whatever revenue they wants from it. Dumbing down the U.I. is a way to do so, as there're far more inexperienced/ignorant/whatever people in the world than experts that need a specialized tool.
What's nuts, because such audience would not pay for the Atlassian services anyway.
I don't like the smell of this.
@Chris_FI was thinking the exact same thing, only without the clever pun. I have a few features I liked that have been removed but I really can't find what they've added since 1.7 that is responsible for the performance issues. It seems like it's just UI changes that no one likes anyway. Also, good luck against the Swans!
I just allowed SourceTree to upgrade itself from 1.7 to 184.108.40.206, the latest version available at the moment.
My first thought was that the UI looked uglier in general, but I can live with that. Now I'm starting to run into lots of usability regressions as well, though:
I've filed bugs for these & hopefully they'll be fixed soon.
SourceTree's UI up to 1.7 was good enough that it was worth putting up with the app's overall slowness. This new focus on performance seems to be coming at the expense of the one thing that made SourceTree stand out - and frankly, the performance doesn't really seem to have improved that much anyway.
Sorry but the new status icon colours are a horribly garish and unattractive combo. Yellow icons on a white background cause them to visually bleed. And saturated yellow, purple and green are a very unattractive combo. The menu icons are uniform and dull pencil lines that are not at all useful in picking out a function quickly. I remember when Firefox for Mac went through a phase like that over ten years ago. Fortunately they got over it quickly.
The items in the repository pane are almost mashed together. Little thought was given to spacing.
@Mike Corsaro Thanks for you response here, unfortunately it is the only "official" one to this point. Yet there is a new version and at first glance I feel like our voices have been heard.
The latest blog post gives a humble response to our criticism for the 1.8.0 and 1.8.1 release - I for one appreciate that and hope that you keep your word in furture releases.
I'd like to point out that I've seen different improvements. Real improvements. But it is still not as good as the design before.
The main toolbar on top looks all the same. When I get tired, it's early in the morning or I just don't have much time I struggle to find the right icon for what I'd like to do.
Additionally if you look at the repositories details (the panel with "File Status", "Branches", "Tags", "Remotes", ...), its the same problem. Plus, the active element (for example the active branch or in the revision list the checked out element) has the tiny circle. As it is the only color thing in there it is dominating in the reception and looks like a major tree entry. In the revision list its not enough to find it when you are fixing bugs and jump all around revisions "binarily", especially when there are a bunch of branches and tags around.
I don't know if its just me, but I'm not having an easy time with the new design and I hope there's room for improvement.
I completely agree... Working with a monochrome interface is like having a conversation with someone that has a very thick accent and not a very good grasp on your native language. You can work with them, but it takes way more effort to extract the information you need, and increases the opportunity for error...
I had to go back to 1.7 straight after updating. Not only did I have the generic monochrome skin, that makes you work harder as you have to check you clicking the right thing every time.
But also, SourceTree told me, after the update, it could no longer see any of my repositories!! I couldn't open any of them.
Very poor effort guys...... really disappointing.....
Very sad to see a lack of care from Atlasssian on this once go to product. I to am looking for a usable replacement.
I understand wanting to make themselves more new with the UI but how hard is it to keep existing functionality OR leaving a original UI mode that with their usage stats would should most will would use.
If more software companies asked their loyal user base, how best to improve their products, success would follow, quickly & efficiently. Many of the suggestions in this feed, would have gone a long way to improving SourceTree. It is a great shame that Atlassian have used a negative feedback loop to achieve this objective. How about asking the question before releasing the update, rather than ignoring comments, once the damage has been done. Atlassian have missed a trick.
I think it is a huge improvement. I waited better design so long and finally it is here. Atlassian, thank you very much.
Icons are awesome, hunks separation in diff pane is more convenient, flattish is beautiful.
However, there are some potential improvements:
@Magnus Bondesson Sorry about that – that issue was my fault and caused by a library that was updated, but not included in the last release. This is a known bug and it will be resolved in a release in a few days.
You can track it here: https://jira.atlassian.com/browse/SRCTREEWIN-4889
Bugs are annoying, but fixable.
But defects-by-design, that's much harder to cope.
Everytime I saw someone saying "beautiful", "sexier", or some other kind of crap about a productivity tool, I promptly think exactly what @Magnus Bondesson though. Or near it, as most of the time it would be just unpublishable. :smile:
Seriously - we are not artists, prostitutes or photographic models. We are developers. We need well made, productivity enhancers, work-flow optimizers tools.
If you want more beautiful, more sexier, more whatever products, you are on the wrong business. Or in need to see a specific kind of movies. :smile:
I agree. It's possible. But it's not a priority. Not even close.
If you can't enhance correctly the UI and at the same time keep and enhance the functionalities, the tool has no use to me - I would be using Git-X or even "git gui" for now, If Atlassian didn't rolled back the tool. Ugly as hell, but they works the way I need.
I need my tools to do the work, not to looks pretty on the screensaver while I'm at lunch. :smile:
Exactly - I care about functional and quick to use not about "beauty". If it looks good that's a bonus, but is probably 4th or 5th on my list of priorities for a programming tool.
Clashing colours work, because it differentiates functions from each other - you can find things quickly. Changing everything to look the same may look nice, but has no use in a productivity/development tool.
UI don't follows the same path of functionalities. It's too expensive to implement a new UI to discover only in beta that it's not viable.
In an ideal world, UI changes are first documented and discussed with representants of the intended audience. Mocks are made, simulations using Photoshop are made. This kind of prototyping would had prevented more than half of the complaints above.
Then the thing is implemented and goes to Alpha to some selected stakeholders that are interested on the success of the tool (and know the thing enough to criticize it). That would have catched about half of the remaining complaints, as the most obvious programming mistakes would be detected.
And just then you go to a public beta.
GitX-dev looks stabler, true.
And in case of Windows I am moving to GitExtensions https://sourceforge.net/projects/gitextensions/
The GUI is a bit ugly, but it is open source and very configurable (also allows custom actions like SourceTree and it is richer in features, it even has bisect, but I haven' tried it yet)
So it is more like a set of tools (also includes adding file log to windows context menu like git tortoise does, which I find very handy).
Also it is more stable than Sourcetree at the moment.
please provide us an option to switch the UI back and forth without losing the current version of Sourcetree.
the new UI looks better at first but it's so buggy and in terms of usability it's worse. I'll give you examples:
I'm still discovering more every time I use it
so please don't force the new UI even if it's going to be finished soon.
Atlassian is persistent! no one is listening and they're still making more updates (more like downdates) .. now the upper bar's icons are broken, they've just shifted the icons down so that they don't have a text label! what a genius workaround. it just sounds like a newbie learning layout building and applying it to the main product.
I'm really disappointed. thanks god I could get the installer for V1.7 and rolled back before I lost my mind.
+1 Daniel - Totally agree! The new UI is pretty fugly. And please, bring back the GitFlow button on the toolbar!
I'm going to try installing an earlier version (windows) or failing that look for a new UI or may even go back to the command line!
Any good alternatives out there?
UI experience is always somewhat "subjective", but it's not only this new UI. It's about all these bugs.
All your shiny new versions introduced regressions! Every x months you come up with a "new UI", meaning to push out a version with bugs!
To not provide an archive with at least the last version to download is NOT user friendly. Your quick response time is no excuse for that!
I agree with that cat!
I agree, version 2.2.2 on the mac is NOT good. it's going backwards. Suddenly half of the stuff does not work. The flat design is a bad idea.
I am going back to the previous version. What was the thinking. If you improve design (allegedly) don't break the features. That's not helping.
Do NOT remove the customize-ability of a software when the majority of its users are programmers who are accustomed to tweak and customize every single corner of their tools.
Alas, like the other competitors there would never be a switch to activate the old theme.
<rant>Don't be surprised if they remove the menu bar and switch to a ribbon, or a minimalistic design. MSFT, GOOG and AAPL are competing on their designs and the fire has spread everywhere.</rant>
I've lost the checkboxes next to the files in the staging interface. I'm trying to get 2500 tests under control, so I make a scripted change to lots of makefiles then review them in the staging dialog. Formerly, I could click the file to view the diffs, then check the box to add the file. Now I'm having to mouse all over the UI and make sure I hit "stage selected" rather than "stage all" which is right next to it. Diabolical! Couple that with the UI losing track of its state when the filesystem notification fires, and suddenly I'm paying more attention to UX issues than my problem domain.
The new UI sucks bad. I can't find anything. atlassian must have had to decide to either lay off their designers or give them BS busy work to do screwing the uI up. Why do companies fix things that are absolutely not broken. The old interface was so simple and easy to use, the new one sucks
The reason software companies change products that aren't broken is so that they can justify keeping their development team employed. Plain & simple. It is an awful justification, but I really cannot see any other reason.
Adding new functionality & fixing bugs is fine, but completely revamping the UI & removing useful features, is totally unacceptable. Even worse, which seems to be the case with SourceTree, is removing features to allow the new UI to function properly. It is never a good idea to prioritise style over substance.
Downloaded 2.5, after being on 1.7 for a while. Flat design is a retrograde step in my opinion. There's no coherent structure, and affordance of the various screen elements is restricted. The tabs are a a prime example. I used to be easy to see at a glance which tab is active, not any more, I mean even Windows 3.x got that right.
I also don't like the wasted space to the left of the diff pane. Just so a lozenge can be shoehorned in presumably to make screenshots look "sexy" or "funky" or something. Always blame marketing :)
Have been looking at alternatives.
That's the thing - if this was a media player or a normal user app the flat new UI would be totally fine.
This is a developer productivity tool. The aim of it is speed and accuracy and to make developers lives easier.
We don't want "sexy" we want "functional", if a UI is ugly as anything, but if it helps me do my job faster or better that's perfect.
Same as the icons down the left, in the old I could tell which were branches, folders, tags or remotes in a quarter of a second without even having to focus my eyes or read it. In the new one they all meld into one and I have no idea what's what.
Windows users can download what I think of as the "latest stable" version of SourceTree (1.7) here:
For the record it still works great and is an extremely useful tool. I have not found the need to search the market for any other solutions.
Be sure to save the Exe file locally, just in case Atlassian decides to remove it in the future. They seem to be very intent on self-destructing.
Thank heavens for this link to version 1.7. I am going to change immediately. The newest version has removed a really useful feature. There used to be file status totals for untracked, modified, removed & renamed files underneath the commit comments box. I used to rely on this so that I could compare changes between local repos using the same code base.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event