Live data from Hacker News

Show HN: Here is our first app after 6 months working on it. What do you think?

yosee.com

41–50 of 51 posts

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#42
post #15

It seems very heternormative. Girls rate boys, and boys rate girls?

Yes, we are planning to add gay/lesbians support, but we have a problem because the comments you post are limited to your gender (girls can see other girls comments, boys can see other boys comments). But we are definitely thinking about it!

There are also plenty of people who are interested in people of two or more genders that you shouldn't erase. This is the kind of thing where, if you really can't figure out how to make it work with your current design, you seriously need to go back to the drawing board.

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#43
Love the landing page. I like the "Absolutely nothing will be published on your timeline..." bit.

I wonder how the Boy rate Girls is going to work for you guys. If you could blog about the stats you get that would be interesting as well! I know this is not the place for that but Lisbon, Taipei and Paris' girls come on top imo.

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#44
post #43

Love the landing page. I like the "Absolutely nothing will be published on your timeline..." bit. I wonder how the Boy rate Girls is going to work for you guys. If you could blog about the stats you get that would be interesting as well! I know this is not the place for that but Lisbon, Taipei and Paris' girls come on top imo.

Thanks! We will talk about some stats as soon as they're relevant.

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#46
post #37

Earlier quoted context omitted.

Yes, we are planning to add gay/lesbians support, but we have a problem because the comments you post are limited to your gender (girls can see other girls comments, boys can see other boys comments). But we are definitely thinking about it!

Uh, this should not be an "oh that's for a future version"...in an urban city (which is presumably where this kind of app would be most used and most useful), you are alienating a good part of the audience. Gender fairness issues aside, this kind of "design" issue raises doubts about how well you've thought this product through. Social/place-rating apps are hard, given the dominance of the big players in this space.…

Yes, you are right and this is definitely top priority.

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#47
post #27

Absolutely beautiful, both the page and the app (though I don't have an iPhone): Are you planning more login API support other than just Facebook? I'd imagine you want to run the gamut: twitter, foursquare, etc - maybe even get rid of your own login altogether to make it easier for people (of course this limits you somewhat - but I'm pretty sure your target audience has at least one of these accounts)

> maybe even get rid of your own login altogether to make it easier for people Please never suggest this to anyone ever again. I'm so sick of having to authorize apps with vague descriptions of what they'll have access to.

Other sites doing something badly does not mean it shouldn't be done.

You're making the generalization that this app will also do it wrong, and maybe that's likely, but I think it's too pessimistic.

If every single application everywhere rolls it's own auth every time, you're going to have 10 auths (which according to security advice should be seperate) to remember.

regardless of implementation the idea of unifying (or even semi-combining) login is not a bad/not worthwhile idea

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#48
post #27

Earlier quoted context omitted.

> maybe even get rid of your own login altogether to make it easier for people Please never suggest this to anyone ever again. I'm so sick of having to authorize apps with vague descriptions of what they'll have access to.

Other sites doing something badly does not mean it shouldn't be done. You're making the generalization that this app will also do it wrong, and maybe that's likely, but I think it's too pessimistic. If every single application everywhere rolls it's own auth every time, you're going to have 10 auths (which according to security advice should be seperate) to remember. regardless of implementation the idea of unifying (…

If every single application everywhere rolls it's own auth every time, you're going to have 10 auths (which according to security advice should be seperate) to remember.

You're confusing with what is [perhaps] technically the most reasonable solution with what your potential users will be willing to do. That's a mistake.

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#49

Your site is nice and it feels well designed. My only complaint is that even on my 100 mbps connection, it took forever to load the content in the smart phone portion of the site. Another question I have is what makes me want to use this as opposed to yelp or foursquare?

We believe that when you choose a bar, or a club, you may want to focus on the people first, and Yosee lets you rate these people and say if they are cool or not. Cool places for cool people. :)

You should change your website to show it off then

Re: Show HN: Here is our first app after 6 months working on it. What do you think?

#50
post #48

Earlier quoted context omitted.

Other sites doing something badly does not mean it shouldn't be done. You're making the generalization that this app will also do it wrong, and maybe that's likely, but I think it's too pessimistic. If every single application everywhere rolls it's own auth every time, you're going to have 10 auths (which according to security advice should be seperate) to remember. regardless of implementation the idea of unifying (…

If every single application everywhere rolls it's own auth every time, you're going to have 10 auths (which according to security advice should be seperate) to remember. You're confusing with what is [perhaps] technically the most reasonable solution with what your potential users will be willing to do. That's a mistake.

isn't thinking about user convenience a good thing?

Can you elaborate? Are you saying that the most reasonable technical solution is what people should select, regardless of what the potential users are willing to do?

Post reply on HN