3 ms·

Andrew, this is cool. Love the name, by the way - "Quirk" for a QR code company is very memorable. A few suggestions: 1) Agree with the other posters about

Andrew, this is cool. Love the name, by the way - "Quirk" for a QR code company is very memorable. A few suggestions: 1) Agree with the other posters about an explanation on the home page. 2) The process by which I had to choose a permalink was confusing - why do I need to choose a permalink before I get my quirk? It would be way more dramatic to have the QR code pop up immediately after I FB connect. This could also help with (1) - you could caption it "This is your personal QR code!" 3) With FB Connect, you can import not just name, but profile photo and other public data. I'd expect you to generate a profile page at my permalink seeded with that information. 4) Obviously, the mobile apps are pretty key. I sent the QR code to my phone via text (I like that feature, btw). But pretty soon it will get buried in my SMS inbox. I need a way to pull it up immediately, like a Quirk app would do. 5) I like the idea of getting conference organizers to embed quirk codes in name cards. But before I would actually do that, I'd probably want: a) Really good profiles at the permalinks b) Customization / branding. It's my conference so I want to promote myself, not getaquirk.com. Branded profiles and conference-specific quirk codes would be key. c) Analytics / insight into how people are using it. Of course that's just my guess - you might talk to some conferences and go through the exercise of selling them on the product to figure out what's truly important to them. (edit - formatting)

andrewacove 16y ago
Thanks Jared. I really appreciate the feedback. > permalinks Your suggestions have convinced me to make two major changes: 1) Users will be auto assigned a permalink and 2) users will be able to change their permalink at any time. I think that having the QR code immediately available will definitely have a greater impact, as you've suggested. I had reservations about user reactions to generated permalinks (for the case when their screenname on the connected network is taken), and about having stale QR codes floating around after a user changes her permalink, but making those changes improves the user experience and mitigates the first concern. Having stale links to Twitter profiles on the web doesn't seem to have been much of a problem, either. There will just have to be very clear, very visible notices that the QR code has changed when a user change her permalink. > FB Connect Detailed profile data is available in mobile profiles, but relies on a separate authorization step. Rather than asking for complete profile access when the user signs up with FB, we request authorization for the individual parts of the user's profile as they choose what to make public. The actual authorization process is (in my mind) the worst part of the Quirk UX right now. That begs the question, would it be better to just ask for full profile access directly from the start? Or will that turn users away? > fast access to the QR code on the phone Making the QR code easily accessible is a major component of the Quirk app. We'll need to find a temporary solution until that's released. Perhaps bookmark and save-to-dashboard buttons are a good step (possibly with HTML5 local store support). > conference customization/branding and analytics Branding conference profiles is definitely a goal. Alot of the focus has been on the mobile experience (which is what most users will encounter if they're scanning other people's badges) - Once the conference features are ready, the conference organizers will be able to push content to profile pages. Branded web(non-mobile) profiles aren't something that has been explored much yet. Analytics of how users are connecting is potentially a huge part of the value offering for this use case. That's a path that I'm very eager to explore now that people can actually connect through Quirk. > profile data Initially, rich profiles are only presented to mobile users. It's primarily a resources issue, and a rich web profile hasn't been built yet primarily because there are other, likely better, places to consume that data from a non-mobile device - the social networks themselves. The stub that's presented now when viewing a profile on the web is mostly a stopgap, but for the moment, traffic is heavily skewed to the web experience instead of mobile, so it probably needs to be built out just to capture new visitors' attention.

andrewacove 16y ago

Thanks Jared. I really appreciate the feedback. > permalinks Your suggestions have convinced me to make two major changes: 1) Users will be auto assigned a permalink and 2) users will be able to change their permalink at any time. I think that having the QR code immediately available will definitely have a greater impact, as you've suggested. I had reservations about user reactions to generated permalinks (for the case when their screenname on the connected network is taken), and about having stale QR codes floating around after a user changes her permalink, but making those changes improves the user experience and mitigates the first concern. Having stale links to Twitter profiles on the web doesn't seem to have been much of a problem, either. There will just have to be very clear, very visible notices that the QR code has changed when a user change her permalink. > FB Connect Detailed profile data is available in mobile profiles, but relies on a separate authorization step. Rather than asking for complete profile access when the user signs up with FB, we request authorization for the individual parts of the user's profile as they choose what to make public. The actual authorization process is (in my mind) the worst part of the Quirk UX right now. That begs the question, would it be better to just ask for full profile access directly from the start? Or will that turn users away? > fast access to the QR code on the phone Making the QR code easily accessible is a major component of the Quirk app. We'll need to find a temporary solution until that's released. Perhaps bookmark and save-to-dashboard buttons are a good step (possibly with HTML5 local store support). > conference customization/branding and analytics Branding conference profiles is definitely a goal. Alot of the focus has been on the mobile experience (which is what most users will encounter if they're scanning other people's badges) - Once the conference features are ready, the conference organizers will be able to push content to profile pages. Branded web(non-mobile) profiles aren't something that has been explored much yet. Analytics of how users are connecting is potentially a huge part of the value offering for this use case. That's a path that I'm very eager to explore now that people can actually connect through Quirk. > profile data Initially, rich profiles are only presented to mobile users. It's primarily a resources issue, and a rich web profile hasn't been built yet primarily because there are other, likely better, places to consume that data from a non-mobile device - the social networks themselves. The stub that's presented now when viewing a profile on the web is mostly a stopgap, but for the moment, traffic is heavily skewed to the web experience instead of mobile, so it probably needs to be built out just to capture new visitors' attention.