Live data from Hacker News

Hoodie – Fast web app development

hood.ie

41–50 of 147 posts

Re: Hoodie – Fast web app development

#41
post #27

So let's just deliver all our business logic as JavaScript to an entirely untrustworthy client! Whats the worst that could happen?

Hoodie works no different than Gmail. What’s the worst that can happen there?

On a related note, how does MailChimp have "confirm subscription" link IN MY GMAIL LIST?

http://cl.ly/image/1o1K2f202T3c

Re: Hoodie – Fast web app development

#42
post #8

Team Hoodie here. Happy to answer any questions you might have :)

Apologies for asking such a horrible question, but is there a rough timeline for it being production ready? It looks very interesting.

no worries, and thanks! Actually, there is already at least one app in production running on it for a few months now plus a few MVPs, so if you want to go for it: do it. We're currently working towards the release of 1.0.

(Disclaimer: Team Hoodie again :) )

Re: Hoodie – Fast web app development

#43
post #2

Broken back button, bleh.

And you thought you were just scrolling... turns out you were navigating.

I wish we could stop calling things "broken" just because they work in a way that's well thought out but unconventional. How are we ever going to make progress on UI design if everyone immediately gets chastised for deviating from more orthodox web behavior by even the slightest amount?

EDIT: lbarrow is correct that the hash tag navigation is borked. I thought people were just complaining about navigation to a previous site on the same tab. I stand corrected, I fully agree it's broken.

Re: Hoodie – Fast web app development

#44
post #41
post #27

Earlier quoted context omitted.

Hoodie works no different than Gmail. What’s the worst that can happen there?

On a related note, how does MailChimp have "confirm subscription" link IN MY GMAIL LIST? http://cl.ly/image/1o1K2f202T3c

Gmail's "Actions" API.

https://developers.google.com/gmail/actions/reference/one-cl...

Re: Hoodie – Fast web app development

#45
post #41
post #27

Earlier quoted context omitted.

Hoodie works no different than Gmail. What’s the worst that can happen there?

On a related note, how does MailChimp have "confirm subscription" link IN MY GMAIL LIST? http://cl.ly/image/1o1K2f202T3c

It's a Gmail feature called "Actions" and was launched back in 2013:

https://developers.google.com/gmail/actions/actions/actions-...

I'm actually surprised so few companies have implemented it thus far.

Re: Hoodie – Fast web app development

#46
post #29

You guys should take a look at http://github.com/EGreg/Q Not released yet -- but if someone has PHP / JS / PhoneGap skillz and wants to work with us, you can be an early member of the community.

In case you were unaware, there's a very popular and lovely promises library for javascript named q.

https://github.com/kriskowal/q

Re: Hoodie – Fast web app development

#47
post #43

Earlier quoted context omitted.

And you thought you were just scrolling... turns out you were navigating.

I wish we could stop calling things "broken" just because they work in a way that's well thought out but unconventional. How are we ever going to make progress on UI design if everyone immediately gets chastised for deviating from more orthodox web behavior by even the slightest amount? EDIT: lbarrow is correct that the hash tag navigation is borked. I thought people were just complaining about navigation to a previo…

This is clearly broken. You can't go back beyond the first part of the page you looked at. It doesn't work.

Re: Hoodie – Fast web app development

#50
post #27

Earlier quoted context omitted.

Hoodie works no different than Gmail. What’s the worst that can happen there?

Well you sure as shit aren't going to see "hoodie.account.signUp(username, password);" in Gmail's client-side code. Gmail's code base is not a "offline first, mobile first" platform. The API that is exposed to the client-side is fairly light (watch the traffic). I highly suggest use research "business logic flaws" in web apps. Anything Jeremiah Grossman has said on this topic is good stuff.

Can you give an example for why that signup code is bad? In the case that I'm using Hoodie with CouchDB, wouldn't Hoodie just AJAX post a user document to the CouchDB _users database (which is a good implementation)? All of the access control would be in the hands of the server with minimal (if any at all) security logic in the front end.
Post reply on HN