[sathomasga]

I merely cited this as one example of a confusing UI, but this response makes my point even stronger. For most applications, the normal user flow is from general (what the app calls Repository Manager, I guess) to specific (a particular repository). Well-designed user interfaces anticipate the typical user flow and give the user a chance to "go back." For example, a user may accidentally click on the wrong repository. That user likely wants to return the app to its previous state so as to make the correct choice.

Neither of these steps really does that. The first opens a command palette which does not have anything resembling a "go back" command. It does list "Recent Repositories," but there is no reason for a user to assume that "Recent" is the same as All the repositories listed on the first screen. The command palette also omits the folder hierarchy present on the first screen, and that hierarchy may be key to finding the desired repo. Opening a new tab is not at all intuitive for a user that wants to go back. And the most obvious result of the command is a new blank screen.

There a lots of things about Fork that look to be very well-done, and it appears to have a great feature set. But if I'm going to use a GUI instead of the command line for git, then I expect the app to be intuitive and easy to use. For me, Fork is not that. I appreciate that other users may have different opinions, and I do wish the developers great success with the project.