Am I the only one seeing the "e" cut off of "you've" on the site? : https://dl.dropbox.com/u/1634015/photos/tapfame.png
on it.
Show HN: Create a portfolio of the mobile apps you've built
21–30 of 31 posts
Re: Show HN: Create a portfolio of the mobile apps you've built
#22Am I the only one seeing the "e" cut off of "you've" on the site? : https://dl.dropbox.com/u/1634015/photos/tapfame.png
What browser are you using?
Re: Show HN: Create a portfolio of the mobile apps you've built
#23Interesting idea! Not sure why but I have only read your main headline when I looked at the page for the third time. My attention was completely drawn to anything below that blue-black bar. It has almost camouflage-like properties. In the featured portfolio all tooltip app names are "App Name".
sorry. fixed the "app name" thing.
Re: Show HN: Create a portfolio of the mobile apps you've built
#24[deleted]
they have a "featured" profile here: http://tapfame.com/daniel.amitay/ But I agree that requiring Facebook is always a big turn off of many people ( me included )
Reasons I didn't sign up for a trial:
* Got Faceblocked.
* No obvious demo until I looked here.
* Demo profile suggests it's iOS-only.
* Demo profile has flawed animations.
Re: Show HN: Create a portfolio of the mobile apps you've built
#25Earlier quoted context omitted.
they have a "featured" profile here: http://tapfame.com/daniel.amitay/ But I agree that requiring Facebook is always a big turn off of many people ( me included )
Reasons I didn't sign up for a trial: * Got Faceblocked. * No obvious demo until I looked here. * Demo profile suggests it's iOS-only. * Demo profile has flawed animations.
Will fix all these issues in the next release. Thanks glimcat.
Reg faceblocked: we'll let you create a portfolio without auth. To get freelance gigs though, you'll need to either FB auth or Linkedin auth.
Reg Demo: redesigning landing page
Reg demo profile: will add a few more demo profiles.
Reg flawed animations: could you be more specific?
Re: Show HN: Create a portfolio of the mobile apps you've built
#26Earlier quoted context omitted.
Reasons I didn't sign up for a trial: * Got Faceblocked. * No obvious demo until I looked here. * Demo profile suggests it's iOS-only. * Demo profile has flawed animations.
Will fix all these issues in the next release. Thanks glimcat. Reg faceblocked: we'll let you create a portfolio without auth. To get freelance gigs though, you'll need to either FB auth or Linkedin auth. Reg Demo: redesigning landing page Reg demo profile: will add a few more demo profiles. Reg flawed animations: could you be more specific?
Not sure is this is what gp meant, but the cycle of screenshots through the iphone screen slide in and out over the whole screenshot of the phone, not just the screen portion.
You should be able to pretty easily play with the positioning and width of the carousel to fix it so they just slide across the screen.
Re: Show HN: Create a portfolio of the mobile apps you've built
#27I'm seeing a pattern here (and this is not a criticism of Tapfame, though I'd love to hear their perspective).
There seems to be general agreement that a startup should build something people want. The most common response here (and with similar apps, in recent memory) is people saying they don't want to have to register with another service like Facebook to use it. And yet, people keep building websites that do just that, and indicate that they will not change this.
Is Facebook so big that startups can afford to blow off everyone who doesn't use it? Is integrating with Facebook's identity system so much easier than writing your own that it saves significant development time? Is there a strategic plan to do something unique with Facebook later?
I'm not saying anyone should do product design by surveying users, and I admit I'm not a great product designer, but when potential users all say "I'm not going to use this product because it makes me jump through hoop X" (and X isn't a fundamental component), my response would be to remove X.
Re: Show HN: Create a portfolio of the mobile apps you've built
#28Earlier quoted context omitted.
Reasons I didn't sign up for a trial: * Got Faceblocked. * No obvious demo until I looked here. * Demo profile suggests it's iOS-only. * Demo profile has flawed animations.
Will fix all these issues in the next release. Thanks glimcat. Reg faceblocked: we'll let you create a portfolio without auth. To get freelance gigs though, you'll need to either FB auth or Linkedin auth. Reg Demo: redesigning landing page Reg demo profile: will add a few more demo profiles. Reg flawed animations: could you be more specific?
The animation of the images sliding goes off the sides of the phone's display area. It would be nice if it were a bit slower as well.
Sounds good, I'll flag it to check out again later.
Re: Show HN: Create a portfolio of the mobile apps you've built
#29You should put up a screenshot on the front page. Also, the demo link just looks like regular text.
Re: Show HN: Create a portfolio of the mobile apps you've built
#30I'm seeing a pattern here (and this is not a criticism of Tapfame, though I'd love to hear their perspective). There seems to be general agreement that a startup should build something people want. The most common response here (and with similar apps, in recent memory) is people saying they don't want to have to register with another service like Facebook to use it. And yet, people keep building websites that do just…
> "And yet, people keep building websites that do just that, and indicate that they will not change this."
IMO there are two salient points to this:
1 - The people who really, really dislike logging in with Facebook (to the point where they will refuse to participate) are a small but vocal minority. Even in the tech industry itself.
2 - The strong dislike for using Facebook login is many-fold. For most people it comes down to abuse of the Facebook link (e.g., spamming things onto your feed, messaging your friends, being in general awful), and that is a trust issue that can be mitigated with the correct positioning and assurances. The people who are against cross-network authentication on principle (as opposed to some negative artifact of its current implementation) are an even smaller camp, and they're the only ones you're really guaranteed to lose out on.
> "but when potential users all say "I'm not going to use this product because it makes me jump through hoop X" (and X isn't a fundamental component), my response would be to remove X."
1 - Beware of what your users say, it is not always what they want, or what they would use. People are extraordinarily bad at guessing their own motivations, if you took all feedback literally at face value, you might be screwed. A complaint against X may be actually a complaint against sub-component Y, or the interaction of X with unrelated bit Z.
2 - The benefit here vastly outweighs the objections. The numbers have shown this again, and again, and again, and again, that when given the option to do a one-click signin vs. filling out a form (and giving out your email address, again), people will overwhelmingly choose the former.