Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

realartists.com

Post reply on HN
Print view View original

71–80 of 106 posts

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#71

Post by mixedCase »

LeoNatan25 wrote: post #51
davidcollantes wrote: post #49

Earlier quoted context omitted.

Just curious, could you link an application using Qt/QML with a native-looking Windows GUI?

Native-"looking" = Looks and feels like nothing native. Always use the best UI for each platform, which is the native UI stack.

Qt maps its widgets to native ones. As long as you pay the same attention to detail as required when you're accessing the Win32 API directly, you're going to be able to get the same results.

And as I mentioned in the other comment, QML makes it fairly easy to make UWP/Metro-style apps.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#72

Post by rtpg »

_xhok wrote: post #64

I'm impressed by the thought, care, and craftsmanship that went into this, and all the more so because it's such a seemingly mundane tool. A better bugtracker UX. What makes this a secretly interesting or important problem?

Well, we have complex e-mail clients right?

Imagine if your e-mail client was like the Github issue tracker. This level of pain is what a lot of larger projects go through. You have tags and basic filtering, but the interface has a lot of friction for "power users" of issues.

Think of those projects with 1000 open issues, and how you would want to deal with this quickly. Easy access to certain filters, an interface with less noise, etc.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#73

Post by kogir »

eschaton wrote: post #69

Note: Not actually native, it's apparently a weird hybrid JavaScript thing rather than a Cocoa app. At least it's not just a wrapper around a WebView. And if that weren't enough, it has some weird server component that's not Github's own API server. That means I won't touch it, because who knows what it's doing or sending…

I'd say it's as native as Mail.app, which also renders HTML content, and relies on a remote server.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#75

Post by userbinator »

mixedCase wrote: post #71
LeoNatan25 wrote: post #51

Earlier quoted context omitted.

Native-"looking" = Looks and feels like nothing native. Always use the best UI for each platform, which is the native UI stack.

Qt maps its widgets to native ones. As long as you pay the same attention to detail as required when you're accessing the Win32 API directly, you're going to be able to get the same results. And as I mentioned in the other comment, QML makes it fairly easy to make UWP/Metro-style apps.

It's easy to make it look native, but in my experience as a user of these usually-ported-from-Linux apps, the difference in responsiveness can be noticeable.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#76

Post by fpotter »

old-gregg wrote: post #62

Fantastic work! Thank you for sharing. Do you guys see pressure from commercial users to offer one-time payment instead of subscriptions?

Thanks! We think the subscription model is the best fit for our product. While Ship is a native Mac app, it also relies on a backend service so we have ongoing costs to cover there.

Also, with subscriptions we don't have to play the upgrade game with our customers. We can release features as they're ready instead of holding them all back so we can justify a $50 upgrade for version 3.0.

That said, we would certainly accomodate companies that find it easier to pay annually. And, if we end up doing an enterprise, on-premise version, that may have a different pricing structure.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#77

Post by pault »

zyxzkz wrote: post #65
kogir wrote: post #63

Earlier quoted context omitted.

We fucked up here, and I apologize. Many thanks to robbiet480 for writing a script to help clean it up. We've just pushed new client and server versions to cleanup hooks when the last admin user logs out. New downloads will be the latest version, and current users can update now using the Ship -> Check for Updates menu option. After that, you can logout using Ship -> Account -> Logout. If you used the app earlier and…

So..., why did you have to install the webhooks in the first place?

> Hooks are added so that Ship is alerted when new repos are created, issues/labels/milestones/comments are added/modified/deleted, issue templates change, etc.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#78

Post by farnsworth »

kogir wrote: post #63
thedjinn wrote: post #35

This app installed webhooks on all of my repos with no automated way to remove them. Very annoying.

We fucked up here, and I apologize. Many thanks to robbiet480 for writing a script to help clean it up. We've just pushed new client and server versions to cleanup hooks when the last admin user logs out. New downloads will be the latest version, and current users can update now using the Ship -> Check for Updates menu option. After that, you can logout using Ship -> Account -> Logout. If you used the app earlier and…

People are used to granting access to an app without assuming that it's going to take full advantage of that access. I have access to a lot of repos. Like, a LOT of repos with a lot of collaborators. And I just had some app add webhooks to every single one. I'm glad I could remove them with 'logout', but I would have really appreciated a more obvious message.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#79

Post by splix »

nicky0 wrote: post #53

I got as far as the screen where is asks for full read/write access to my code, including all my private repos. I'm fairly sure you won't mess anything up or steal my secrets, but why does it need this?

That's what stopped me from using this app. I can't give it access to most of private repos (because NDA and other stuff), and don't have any plans to use it with that repos. What I wanted to play with some public repos, just to see how it works. Apparently I can't do it w/o giving access to private repos too.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#80

Post by hobarrera »

kogir wrote: post #63
thedjinn wrote: post #35

This app installed webhooks on all of my repos with no automated way to remove them. Very annoying.

We fucked up here, and I apologize. Many thanks to robbiet480 for writing a script to help clean it up. We've just pushed new client and server versions to cleanup hooks when the last admin user logs out. New downloads will be the latest version, and current users can update now using the Ship -> Check for Updates menu option. After that, you can logout using Ship -> Account -> Logout. If you used the app earlier and…

I wish we'd see this more often. You fucked up, but came clean about it, apologized, and gave a working solution. Congrats!
Post reply on HN