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

Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

medium.com

Post reply on HN
Print view View original

21–30 of 56 posts

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#21

Post by cdolan92 »

burnout1540 wrote: post #17

Co-founder and CTO of HelloSign here. Sorry to hear that OP's bug reports weren't taken seriously. Good tech support is a must for mission critical APIs. At HelloSign we take great pride in our API and our tech support. Rather than outsource support or rely on less technical people, we have our developers directly support the API they built. So when you give our API a try, I encourage you to check in with one of our…

Personal note - HelloSign and HelloFax are sweet. We use HelloFax alot more than Hello Sign, but both made my startup's daily operations a lot easier.

Highly recommended, and we've been with them for 2+ years!

Disclaimer - Never used the API, just like the service and its Box integration

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#24

Post by zem »

offtopic, but "plodding craftsmanship" is a more attractive job descriptor than any number of "ninja", "rock star", "changing the planet" and other such overinflated and overused terms. reading between the lines, it means that the company values both doing things right and taking their time to make sure they've done it right, which is the exact thing that both drew me to and keeps me happy in my current job.

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#25

Post by JohnTHaller »

Jemaclus wrote: post #2

One of the biggest pieces of advice I have for junior devs (and software engineers in general) is actually quite simple: Remove the phrase "it works for me" from your vocabulary. The rationale is equally simple: I wouldn't take the time out of my day to send a bug report if it "worked for me." The problem could be any number of things: buggy code, incorrect instructions, browser incompatibilities, race conditions. Wh…

"It works for me" is a great first step. More specifically, it works for me on Windows XP, Vista, 7, 8, and 10 TP (since they're all ready in virtual machines) is an even better one. Followed up with the usual questions of What operating system are you using? 32-bit or 64-bit? What's the full install path? What antivirus product and version is running? What software firewall, if any, is running? Any other apps running? New install or upgrade? Etc. I have some of this built into the About box of one of my apps and am adding in the rest shortly.

Quite a few "bugs" are no fault of the developer/publisher. But learning where those issues are and letting your app alert/inform the user what's going on as they install to an invalid location or break their TEMP directory thinking they're protecting their machine or remove IE from Windows using a broken 3rd party utility or use an antivirus product that gets more wrong than right, etc... can help cut down on the bug reports, help the user from making 'mistakes' they shouldn't be allowed to make, and just make the whole process easier.

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#26

Post by vivekajayshah »

burnout1540 wrote: post #17

Co-founder and CTO of HelloSign here. Sorry to hear that OP's bug reports weren't taken seriously. Good tech support is a must for mission critical APIs. At HelloSign we take great pride in our API and our tech support. Rather than outsource support or rely on less technical people, we have our developers directly support the API they built. So when you give our API a try, I encourage you to check in with one of our…

We have used Hellosign for years, and they are modern, awesome, and always responsive.

We did a case study here - if that helps: http://blog.hellosign.com/simplyinsured-leverages-esignature...

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#27

Post by mmmmax »

vivekajayshah wrote: post #26
burnout1540 wrote: post #17

Co-founder and CTO of HelloSign here. Sorry to hear that OP's bug reports weren't taken seriously. Good tech support is a must for mission critical APIs. At HelloSign we take great pride in our API and our tech support. Rather than outsource support or rely on less technical people, we have our developers directly support the API they built. So when you give our API a try, I encourage you to check in with one of our…

We have used Hellosign for years, and they are modern, awesome, and always responsive. We did a case study here - if that helps: http://blog.hellosign.com/simplyinsured-leverages-esignature...

Same here -- never had a problem with the product or customer service

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#29

Post by donbronson »

As a user, having to file a form using EchoSign, I would to cringe. It requires flash and has some really bad usability. An example of that is requiring at least two non-standardized date formats. UX is important for forms because humans make errors when information is not clear.

Re: Why, after a year with Adobe EchoSign, I’m taking my business elsewhere

#30

Post by function_seven »

mreiland wrote: post #20
eropple wrote: post #12

Earlier quoted context omitted.

> even from QA departments You were saying? Also, do note that he edited in that last graf after he posted it. It doesn't help much, though.

I was saying you're an asshole for conflating the two. Did I misspeak?

[chx] > Sorry but most bug reports, even from QA departments are noise at best, nuisance at worst.

[eropple] > Your experience certainly doesn't match my experience; I've worked with brilliant QA people who were able to diagnose problems both when deviating from spec and when performance is a feature that isn't being properly met.

chx conflated the two, not eropple.

Post reply on HN