Author Archive

  • Wed, Mar 28 2012

    As we have made changes to our process to address the issue of similar submissions, we have attempted to create a system that protects people who submit unprecedented ideas. We now have a mechanism for surfacing ideas that are similar to those we place Under Consideration. We review these similar ideas, and if it is determined that an idea we are interested in has been submitted previously, in a form that encompasses the aspects that interest us, we reward the inventor credit to the submitter of the original idea.

    After seeing this system work for products such as the Double Sided Iron, and the Emergency Sign, we have decided to make an adjustment to the process. Moving forward, and applying retroactively to the Emergency Sign, and Double Sided Iron, we are going to reward 10% of product influence to the submitter, voters, comp shoppers, and revisionists (revisioners?) of the ideas that make it to Eval, but are ultimately not selected because of an earlier, similar submission. This influence will not come come out of the 60% allotted normally for Eval.

    We have come to this decision because it is our goal to reward people for influencing the development of Quirky products. It is clear that the submissions that spark our interest in an idea are influential, even if those submissions are ultimately not selected because of a prior idea. We want to make sure the users that contribute to those catalyst ideas are not left unrewarded.

  • Mon, Feb 20 2012

    There will be a small maintenance period tonight between 11:30 and 11:59 pm EST. We will be pushing new updates. If everything goes well, the actual downtime should be less than 5 minutes.

    -Nathan

  • Thu, Feb 16 2012

    Thanks to everyone who joined us for the town meeting today. For those who couldn’t watch live, or want to go back and review, here are the slides and the video:


    Town Meeting: Feb 16, 2012

    View more presentations from quirky



    Video streaming by Ustream

  • Mon, Feb 6 2012

    Eval Vote Change

    By nathan at 2:41 pm

    Effective immediately, we have changed our algorithm for rewarding voters of successful products during eval.

    The previous algorithm rewarded influence based on the proportion of votes cast overall to the proportion of votes cast for products that went on to be marked Under Consideration (with larger portions given to ideas that were ultimately selected).

    There were two main problems with the former system:

    1. Clarity – Due to the complexity of the old system, it was hard for users to tell how much influence they stood to gain from voting on an idea at any given time. It was also a challenge to understand for users unfamiliar with the system.

    2. Influence amounts – Many people are casting extremely large numbers of votes (sometimes upwards of 150 per day). Because they cast such a wide net, they often are awarded for ideas that go under consideration. However, because they are penalized for the number of votes they cast overall, their experience percentages tend to be minute to the point of absurdity. This is a bad experience for everyone involved, and we want to encourage people to vote for ideas they like, not to simply hedge their bets by voting for as many ideas as possible.

    To that end, we are changing the influence algorithm for voting, effective immediately. As before, at the end of every eval round, two groups will be awarded influence for each winning product: 1) people that voted for that product, 2) people that voted for products that were under consideration, but were ultimately passed on during the course of that round. However, instead of diluting influence on a per user basis, each voter will be given the same amount of voting influence, depending on which of those two groups they belonged to. The catch is that users will be limited to casting 15 votes per day. The vote count will reset each night at Midnight EST. Votes cast prior to this change will stand as is.

    The 15 vote limit is a measure to prevent over-voting (voting on as many possible ideas in order to have a better chance at getting influence). As such, there will be no rollovers on unused votes from day to day. We realize that not everyone can log on to Quirky every day, but 15 votes per day is meant as an absolute maximum. We are not trying to encourage people to use every possible vote; we are trying to encourage people to vote for the ideas they like the most.

    As with everything at Quirky, this is an ongoing experiment. We may change things in the future based on the results. Possible future changes may include adjusting the amount of daily votes up or down, awarding additional daily votes to certain groups based on merit, and eliminating influence for votes on non-winners.

    As always, thanks for sticking with us as we strive to make invention more accessible.

    Nathan

    (edit: the system resets at Midnight EST, not GMT)

  • Tue, Dec 27 2011

    One of the winning ideas this week was a hairbrush with retractable bristles that is easy to clean. This idea was submitted in one form or another by three different users (that we know of), which means that we have to make a judgment as to who is the original inventor.

    We have decided that the winning idea is Vicky Laursen’s (http://www.quirky.com/ideations/145817). The reason for our decision is that Vicky’s (original) idea was posted first chronologically, and the idea was active at the time of selection. The other two ideators (http://www.quirky.com/ideations/133330 & http://www.quirky.com/ideations/144164) will still be eligible to gain influence in the upcoming concept round, in which more influence than normal will be distributed, owing to the relative openness of the winning concept.

    We are currently working on a system to let users identify potentially duplicate ideas; until that is in place, please notify us of issues at similar@quirky.com.

    -Nathan

  • Wed, Dec 21 2011

    We are going to begin issuing social sales make up rewards in the next 48 hours. These rewards are to address lost referrals from flaws that existed in the system between 10/20/2010 and 7/7/2011 that caused some orders not to be attributed to valid referrals. The make up amount for each user will be $.01 per referral attributed to that user during the period between 10/20/2010 and 7/7/2011. This amount is 2x the value of the average referral. Thank you very much for your patience while we worked through this tricky issue.

    Additionally, in the next 30 days, we will be rolling out a new referrals system that rewards Quirky users for signing up new users, in addition to rewarding for marketing Quirky products. This system will be more simple, and should be far more lucrative to Quirky users.

  • Fri, Jun 25 2010

    Iterations

    By nathan at 11:37 am

    The iPhone 4 Launch at Apple SoHo

    I made a point to walk past the Apple Store on the way to work yesterday morning, and while doing, captured the above shot of the line. The store entrance is clear on the other side of the block, and the line snaked around the corner onto Mercer Street, so it essentially took up a whole city block. It’s fun to see people so excited about technology.

    In the spirit of the iPhone, which seems to be growing in popularity despite the fact that each release is comprised of a relatively small set of new key features and improvements, I thought I’d talk about some of the small (but hopefully meaningful) changes we have made to the Quirky platform recently.

    One of our highest priorities is continually improving the speed of the site. Quirky.com is essentially a tool. Like any implement, is should be an unnoticeable helper, not a hindrance to its higher purpose. In order to make the job of contributing and improving ideas as easy as possible, the site needs to load pages extremely quickly; the more ideas a user can consider/submit in a given amount of time, the better the process works.

    If you have been reading the blog (or frequenting the site), you are probably aware that we had a bit of downtime on Tuesday. What we were doing behind the scenes was moving our database from a small Amazon EC2 instance to a large Amazon RDS instace. We have been seeing a steady increase in site traffic, and what this means is more database hits. When you try to query an overloaded database (querying happens when you load a page on the site), it is like waiting in a long line at a supermarket without enough checkouts open. It takes forever, and lines start getting backed up into places they shouldn’t, like the aisles. The only way to solve the problem is to add more checkouts, which is what we did on Tuesday. Our new database should have about 4x the capacity of the old one.

    The second change we made related to speed was adding asynchronous processes to the platform. That is a geeky way of saying that we made it so the platform can do some stuff in the background while other stuff is happening. For example, when a user uploads a picture with an idea, we need to do some stuff with it before it is ready to use. We need to create versions of it in a bunch of different sizes for different places on the site (which is slow), and we need to upload all those versions to our CDN (which is way slow). During all that time, if we are doing things synchronously, the user is waiting for the page with his/her completed post to load. If we offload all that work to a different process, however, we can just load up the completion page with indicators that the processing is happening, and replace those indicators with the actual pictures once everything in the background is complete. This way, it is the user’s choice whether to wait around and see what happens, or simply move on to the next task. This pattern works well in situations where the user may or may not care about the result of a particular job, and really, really well in cases where a long running task is completely opaque to the user, like when we need to distribute out rewards to influencers when someone makes a purchase on the site. As much as the influencers themselves may care about this process, the person buying the product really just wants to see the purchase confirmation and get back to browsing icanhascheezburger or Perez Hilton or whatever. The faster buying process equals a better user experience, and the better user experience equals more future sales, and more money for everyone.

    Anyway, I hope that sheds some light on what we have been putting our efforts into recently. We have also made numerous other smaller changes (including user requests like comment notifications) that we will be trying to roll out in the next week or so. Please keep the requests/complaints/random observations coming.

  • Thu, May 27 2010

    A Common Thread

    By nathan at 3:12 pm

    Hi, I’m new here. My name is Nathan Smith.

    I am a Silicon Valley refugee. I grew up in a tiny town in California and moved to San Francisco after graduating from UC Davis. I worked as a programmer there for four years before coming to live in New York last Friday.

    Although I am new to New York, and new to Quirky, there is one aspect of all this that is quite familiar, which is the desire to work together to create something great.

    There is a strong technology subculture in San Francisco (although I’m not saying by any means that SF is the only place where this subculture exists). It is literally hard to walk into a bar in some neighborhoods without hearing someone talking about functional programming, or data mining using MapReduce, or some other incredibly dorky (awesome) thing. In this subculture, community involvement and openness are the norm.

    Consider Cassandra, the NoSQL database that Facbook developed and open sourced. Although there are other exceptional NoSQL databases, MongoDB for example, Cassandra garnered a huge amount of attention because Facebook developed it (and Twitter subsequently announced they were going to adopt it). This has lead to widespread community involvement in the project, which has in turn propelled it from science fair status to production ready in a tiny amount of time. It is now used on numerous high profile products/sites like SimpleGeo, Digg, and WebEx. Cassandra changed the way people think about scaling data storage, and it never could have done without the community pushing it forward.

    Now, Cassandra is admittedly a niche product, an intangible piece of logic built by engineers for engineers. However, there are also precedent for this process succeeding in creating a consumer-facing product. I recently attended Google’s developer conference, Google I/O, where the mood could really only be described as exuberant. Sales of phones that run the Android OS outpaced the iPhone in Q1 on 2010.  In three years, the Android OS was taken by Google and the community from nothing except the idea world needed an open source phone platform, to a fully functioning piece of software that was succeeding in an incredibly competitive space. I think the most exciting thing about the whole situation are the possibilities it invites. If you can take on Apple and the iPhone with an open product and win… well, you know what I mean.

    I am incredibly excited to be here at Quirky because I know the process works. I know that the many consistently outperform the few. I can’t wait to see what we build.