from Hacker News

Kicksend Practices Part I – Backend & Web

by skyfallsin on 6/25/12, 11:11 PM with 9 comments

• by huhtenberg on 6/26/12, 12:22 AM

  Please tell us about your business model. It is far more intriguing :)

• by iaskwhy on 6/25/12, 11:53 PM

  Please change the link of the logo to the homepage of the site and not of the blog (or put there a link somewhere to the homepage, "Send Files" is not obvious enough).

• by Smudge on 6/26/12, 12:11 AM

  > The Kicksend web app [...] consumes our API the same way as our other apps do.

  A result of this is that your app does not work if javascript is disabled. And as a NoScript user, I'll have to carefully consider if I want to whitelist you. (Hint: Quite often, I don't bother. Especially if the site doesn't at least degrade politely ["We're sorry, but our service requires JS..."], which Kicksend does not.)

  Don't get me wrong -- I think this is a very clean solution. There are just trade-offs to consider. And, to be fair, enabling both client-side and server-side consumption of an external API -- all within the same app -- is probably more of a headache than it is worth.