A blog on novel user interfaces, mobile applications, pervasive and ubiquitous computing. I use the blog as a note pad ;-)

Monday, 1 June 2015

Crowdfunding - Interviews with Amanda Williams and Khai Truong

In the next issue of the IEEE Pervasive Magazine I will publish in the column on Innovations in Ubicomp Products the article: "Crowdfunding for Ubicomp Products: Interviews with Amanda Williams and Khai Truong" - Here are already the full interviews.

Interview with Amanda Williams

Albrecht: You had a successful kickstarter project with a
"lamp" – can you shortly describe the product (perhaps you have one
or two photos, too)? And who was on the team?

Amanda: Our kickstarter campaign was for a smart, programmable lamp named
Clyde. Clyde is a unique, jellyfishlike desk lamp that does both bright task
lighting and colored ambient lighting (see figure CLYDE). He comes
equipped with environmental sensors that he automatically detects and reacts
to, so whether you want him to be "touchy feely" or "afraid of
the dark", you can change his personality without programming. But if you
do want to program (or learn how) Clyde is Arduino compatible and open-source,
and we provide a number of guides and tutorials at http://fabule.com/clyde/.

Our team during the crowdfunding and manufacturing process was composed
of myself, Bruno Nadeau, and Angela Gabereau. I did a lot of the interaction
design, electrical engineering, marketing, and customer engagement; Bruno
handled the design of the physical enclosure, design for manufacture, firmware,
and testing -- he spent the most time on the factory floor; Angela is an
all-round great software engineer, so she contributed to firmware development,
coding up some of our test software, and setting up the back end on our website
for ecommerce and customer support.

Albrecht: Why did you go with crowdfunding? What were the
advantages for you over other funding approaches?

Amanda:If you're starting a company with a hardware product, your typical
startup funding options tend not to match your cost structure because they are
really optimized for software companies. If you're creating a software product,
your major expense is just developer time; in the early stages you'll have
founders working for nothing, which means your expenses are almost nil. As
little as $25-50k in seed funding from an angel or an accelerator can get a
software startup to the point where it has traction, customers, and revenue - if
the founders handle everything really well. This is virtually impossible for a
hardware startup, no matter how disciplined the founders are, because they will
have to deal with the costs of materials, manufacturing, and shipping physical
products. And certifications, which are a significant cost and a real hurdle
for people who don't have prior manufacturing experience. Costs vary depending
on the product, but I think it's pretty rare to be able to do this well for
less than $100k, and even that is a stretch for all but the easiest hardware
projects.

So you have this chicken and egg problem. Investors (quite reasonably)
don't want to part with a ton of money until they see that your business can actually
sell a product; but it takes a lot of money to manufacture a product that you
can sell. This is where crowdfunding comes in. It can provide the money you
need to cover non-recoverable expenses, and if it goes well, it shows potential
investors that you have a market for your product.

There are a number of risks here. Crowdfunding can help you succeed, but
it can also give you enough rope to hang yourself with. A failed campaign -- or
even a fairly lackluster success -- can actually hurt your chances of
attracting investors. It's also extremely common for first-time project
creators to underestimate their expenses. People worry a lot about their
campaign failing, but that's not the worst outcome. The worst outcome is if it
succeeds, you take on the obligation to deliver what you promised, and then you
run out of money without delivering. In my experience, I see it becoming
increasingly common for startups to start fundraising the moment their campaign
wraps up, without waiting to deliver the actual product. I think that's the
smart thing to do. It's a moment where your company and your product is all
potential: you've shown you have traction, but you haven't yet had the chance
to make any ugly manufacturing mistakes. Securing conventional funding to supplement
the crowd-funding helps insure against the possibility of running out of cash
before you deliver.

Albrecht: Can you give a short overview of your timeline - from
idea, to running the kickstarter campaign, to delivering the final products?

Amanda:Our original idea evolved a lot over time. Around January-April 2012 we
were working part-time on these LED solder kits, playing around with the idea
of an electrical kit that we could build up into various different mechanical
configurations. So we made a little solder kit of PCBs with a few through-hole
components, as well a couple different laser-cut enclosure kits: one of which
would let you build a soft ambient light, the other of which would let you
build a little desklamp with an adjustible neck -- identical PCBs in both. We
brought these kits to Maker Faire in the Bay Area and to a big "Maker
Carnival" in Beijing, the first such event to be held in China. We were a
bit surprised to see how much people were drawn to the attractive enclosure design
we'd worked on, people who aren't usually that into solder kits. So we started
considering how we might make these kits more approachable to a broader
audience.

We submitted our idea to HAXLR8R, a hardware accelerator based in
Shenzhen, and were accepted to the program. This meant that Bruno and I moved
to Shenzhen in January 2013 to spend almost four months doing intensive product
development. While we were there, we had access to fabrication techniques that
we couldn't have afforded back home. We could cheaply CNC or vacuum cast really
professional-looking prototypes, the kind of thing that you could imagine on a
store shelf. We could also prototype more sophisticated electronics much
faster. This enabled us to move away from solder kits (4 out of 5 people who wanted
to buy our product at previous maker faires didn't know how to solder) to an
Arduino-compatible board with auto-detectable sensor modules. We now had a
product with a really gentle learning curve, allowing users to customize
without any special tools at all, but still open enough for really deep
hardware or software hacking. Also, we were able to make it look really cool!

We ran our Kickstarter campaign from May-June 2013 and made almost
$150k, more than triple our goal. We thought we could deliver the product by
Christmas, but because of our inexperience, we underestimated how much work was
still required to design for manufacture, set up a test plan the factory could
follow, finalize and purchase everything on the bill of materials, design
supplementary materials like packaging and manuals, test for electromagnetic
compatibility, and ship to 30 different countries. During this time we had to
re-design our board because the microprocessor we were using suddenly shot up
in price. We had to do more mold revisions than anticipated, and switch
materials to a plastic that would look good when back lit by a bunch of really
bright LEDs. Since we were using several different materials in our product --
injection-molded plastic, die-cut silicone, metal gooseneck tubing,
off-the-shelf screws and nuts, and custom PCBs -- we had to work with a number
of different, but interdependent suppliers. If one supplier has a delay, the
others fall like dominoes. In hindsight, a lot of this stuff looks obvious, but
our experience wasn't really atypical for first time product creators.

We shipped Clyde out to our backers and post-Kickstarter pre-orders in
July of 2014. One typically thinks that shipping is the finish line, but the
reality is, that's when you start seeing a lot of customer support work. It's a
computational product, so of course, you have to answer questions about set-up,
drivers (if anyone wants to plug it in to program from their computer), how the
sensors work, how to assemble, etc. Sometimes things get held up in customs,
sometimes packages go missing and need to be replaced. So that will take up a
lot of your time for a few months, and customer support is never really an
engineer's favorite task.

Albrecht: What was the minimum number of items that were required in order to
make sense to start production and why? Is there an "Economy of
scale" for Ubicomp products?

Amanda: There is ABSOLUTELY an economy of scale for Ubicomp products, though it
depends a lot on your method of production. More and more manufacturers in
China and North America are willing to do small runs, but it will inevitably
cost more per piece.

When we were calculating our Kickstarter goal and reward levels, we
calculated how much we would need for runs of 300, 500, and 1000. We ended up producing
a run of 1000, plus 100 wooden special edition Clydes. (Note: I don't recommend
Shenzhen for woodworking.) The cost of tooling for injection molding is high no
matter what (we paid $10,000, and that was a remarkably good deal), but the
more you make, the more that cost gets amortized across many units; and the
unit cost itself also go down. If you've ever prototyped hardware and shopped
for components somewhere like Digikey or even Sparkfun, you're probably
familiar with the idea of price breaks for electronic components: each
capacitor costs half as much if you buy 1000 instead of 10. The same logic
applies to injection molded plastic parts, too. Every time you do a
manufacturing run, a skilled technician has to set up the injection molding
machine. They have to get the mold temperature, plastic temperature, injection
speed, and release of air pressure calibrated exactly right for the size and
shape of your product, and this takes a lot of trial and error. Once that's
done, it's easy to spit out one unit after another; but you can see why
manufacturers would prefer to do 10,000 units at once rather than 1,000 ten
times. The calibration process also generates plastic waste that can't be
recycled since it's often warped and burnt.

Method of production matters a lot. Injection molding, as described
above, has a very high up-front cost and a low per-piece cost. However, if you
happened to be making something using CNC milling, you'd have a fairly low
set-up fee, and a relatively high per-piece cost. This really needs to be taken
into account when you set up a crowdfunding campaign. Campaigns that go way
over their funding goal are actually MORE likely to experience delays, and I
suspect that a lot of pain could be avoided if creators thought ahead about whether
their production methods scale well or not.

Albrecht: Ubicomp products typically include design, hardware and software (and
often networking) and I guess you had the know-how for prototyping yourself /
in your team. How did you transfer the expertise for prototyping to production?

Amanda: We learned the hard way. Bruno is extremely organized and
detail-oriented, and it is absolutely crucial to have someone on your team like
that. I turned out (to my own surprise) to be ruthless - kind of tactically
evil, in fact - when it came to negotiating prices with suppliers; you probably
also want someone like that on your team.

If you can hire a senior engineer with lots of manufacturing experience,
that would be ideal. Most of us don't really have the budget for that, so we
muddle through.

That said, we had great mentors. Bunnie Huang helped advise us on some
manufacturing issues, and he's been a wonderful resource to us, other hardware
startups, and even graduate students looking to manufacture creative hardware.
Our own contract manufacturer (AQS), since they often work with startups, was
willing to show us the ropes -- not everyone would have been so patient. It
costs a bit more to work with a factory like that, but I'd say it was worth it.
And we were also working in an environment where we had frequent contact with
other teams who were doing similar work to us. So we could always talk to
someone who was a year, six months, two months ahead of us in the process, and
anticipate what might go wrong. And in turn, we helped teams that were a few
months behind us.

Learning to manufacture is not easy, and it's not at all formalized.
Most of us learn by forming professional networks and getting help from our
friends. You have to be resourceful, and not shy about asking for help.

Albrecht: With crowdfunding you have customers for a product often already at the
idea stage. How does this impact the product development and the final
implementation?

Amanda:It's great! And it sucks!

Most backers are really supportive. They back campaigns not just to
acquire an end product, but to engage with the process of invention and design
and production. So you can get great feedback from people regarding what
features they want you to prioritize. We opened up our source code and saw
people creating new modes of interaction for Clyde, and it was awesome. I'm
eternally grateful to the 965 people who gave us a chance.

But it does add a lot of pressure. Even if people are nice, you feel the
weight of your promise to give them what they want, and you feel pretty awful
about every delay. I love learning new things, but it's more pleasurable
without all the pressure!

Albrecht: How is crowdfunding changing how we make ubiquitous computing
products? Are there new classes of products that become economically viable?

Amanda: Crowdfunding, along with a growing class of manufacturers that are
willing to do small runs, allow us to actually bring more long-tail, niche
devices into existence. Clyde's a pretty niche product. It's a quirky design.
It's not meant to be one-size-fits all. 1100 was a pretty good number to
produce. If we'd been required to do a minimum order quantity of 10,000, it
just wouldn't have happened, but this way, about 1000 people get a neat little
product that powerfully appeals to them. But I think also these small
manufacturing projects have to be quite passion-driven, since the up front work
to design a 1000-unit run is not much less than the work required to set up
something much larger. You probably won't get filthy rich doing this stuff, but
if you handle things right, you won't go broke, either.

This new set of capabilities makes the boundary between research and
product-development a lot more porous. You could conceivably do a run of a
hundred or so devices for a research project, and deploy them in the wild for
validation. Universities and industrial research labs spin off research
projects into startups sometimes; crowdfunding and small-run manufacturing can
allow you to validate these projects before taking a big risk on them.

Albrecht: With crowdfunding you give your idea away (or at least you make it
public) before you can ship. Were you afraid of others being faster in creating
"your" product and having it on the market first? Did you take
precautions to avoid competition?

Amanda: Protecting our IP wasn't a huge deal for us, but it can be for others.
At $150K, we were below the threshold of interest for most copycats to try to
reverse engineer our product -- if we'd raised more than half a million I'd
have been a lot more worried. But anyway, we made it all open source.
Preventing copying wasn't a huge priority for us. It is for others.

In the US you get a one year grace period between going public with your
idea and filing a patent for it. This doesn't apply everywhere, so if you want
to patent, submit it before you launch a crowdfunding campaign. However, patent
protection is far from air-tight. Whether your patent protects you or not is
really for the courts to decide, if you ever get into a lawsuit. Do you have
the budget to hire a lawyer for this? A better lawyer than Xiaomi can afford?
If you have a US or European patent, that won't count for anything in China.
You can get a patent in Hong Kong if you're willing to translate everything,
and the People's Republic of China will *ostensibly* honor it. But I will eat
every ounce of our plastic waste if Chinese courts EVER rule in favor of a
foreign company suing a Chinese company for patent infringement. In fact, I
believe you have to set up a China-based subsidiary to even be allowed to sue.

So if patents are not that useful, what do you do to protect your
product? You have a couple of options. 1) Move fast. Invent new things faster
than people can copy your old things. But watch out, those shanzhai
manufacturers are pretty quick. 2) Don't make incredibly simple pure-hardware
products. Those are the easiest things to copy. They're right in the shanzhai
manufacturer comfort zone. If you're doing something incredibly original in
hardware, something that required lots of R&D to get right, that can help a
lot. Or you can put a lot of the value in software and the creation of an
awesome UX. If you're worried about how honest your manufacturer is, don't give
them the source code -- just have them flash the binaries onto your
microprocessors, or if you're really paranoid, do it yourself (we know someone
who did that). The hardest thing for a competitor to steal is a fantastic user
community.

That said, I really respect those shanzhai guys. Silvia Lindtner and
Bunnie Huang have both written about what that work looks like on the ground.
They are extremely clever about using their hardware ecosystem to reduce costs,
and they create niche (or not-so-niche) products for markets that mainstream
companies aren't touching, like a minimalist mobile phone that retails for 12
USD! That means the cost of materials, labor, and shipping have to add up to no
more than 4 USD. That is pretty crazy.

Albrecht: How did you continue after "kick starting" you project /
company?

Amanda: Manufacturing Clyde to fulfil our Kickstarter was a marvelous learning
experience. Once we finished up that project, we realized it had given us a ton
of ideas for tools that we wished we'd had during the manufacturing process.
Effective collaborative tools for manufacturing just didn't seem to exist yet,
at least not in any form usable to the increasing number of startups and
small-scale creators that need them. We're working on an exciting new project
now (up on fabule.com) for a hosted Bill
of Materials management tool. The Bill of Materials is a keystone document that
is an absolutely crucial point of communication between a creator and their
manufacturer, at all stages of production, from prototyping, to sourcing, to
assembly, testing, and subsequent manufacturing runs. Right now everyone is
using Excel, and spending hours doing tedious and error-prone revisions, and
maintaining multiple parallel copies for different purposes and different
audiences. We've spoken to manufacturers who've had to spend hours coaching
startups on how to provide them with the specific information they need to even
be able to provide a quote. We know we can do better. At this point we're
decent domain experts in hardware manufacturing, but we also have a really deep
background in UX and software development, which means that we're really
well-positioned to build a tool that can help guide first-timers to do the
manufacturing collaboration correctly.

In the hardware ecosystem right now, we're seeing a revolution in
prototyping technologies and fundraising techniques. The first two steps in
creating a ubicomp product have gotten much, much easier, and it's opened the
field up to a lot more people. However as soon as you face the problem of
manufacturing, you find that that part is about as hard to navigate as it ever
was. So now we're tackling that step, trying to find ways to standardize,
educate, and create smoother collaborations between creators, manufacturers,
and suppliers.

Albrecht: Further comments?

Amanda: When we make ubicomp products, we are often trying to make
"normal" objects smarter. We stuff processors, and wifi or bluetooth,
and batteries, and tiny circuit boards into everyday things like lamps,
jewelry, cat toys, bicycle handlebars, cribs, etc. But the manufacturers who
know how to make lamps, jewelry, cat toys, bicycle handlebars, and cribs don't
necessarily know ANYTHING about manufacturing and testing computational
hardware. And the manufacturers who know how to make and test PCBs don't
necessarily know how to work with the materials that you'd need to make your thing.
So when we try to make smarter everyday things, we often find ourselves in the
position of having to educate our manufacturer, or at least we have to be a
good bridge between manufacturers who have very different areas of expertise.

Short bio:

Amanda Williams is Co-Founder and CEO of Fabule Fabrications. She's in
charge of creating beautiful interactions, beautiful hardware, and customer
development. She has a Ph.D. in Information and Computer Sciences from UC
Irvine and a B.S. in Symbolic Systems from Stanford University. Amanda has
worked at Xerox PARC, Adobe, Intel Research, and Microsoft Research.
Indecisively, she loves both qualitative user research and hardware design. She has been accused of eating like a trucker.

Interview with Khai Truong

Albrecht: You had a successful indiegogo project with a
on-screen keyboard – can you shortly describe the product (perhaps you
have one or two photos, too)? And who was on the team?

Khai: Minuum is an text input method which reduces a full size keyboard down
to a single dimension (or row) of keys. For on-screen keyboards, this reduces
the amount of space that would be taken up by the input method, giving more
real estate to the rest of the application. The challenge introduced with
enabling this is how to allow users to still type quickly as it becomes harder
for them to precisely hit keys on this reduced sized keyboard. To this end, the
backend of the product is a disambiguation engine that predicts what the user
is typing without requiring the user to always hit the exact keys in the word
that they are typing. By reducing text entry to being simply selection of keys
placed on a single row, this same mode of typing can be carried over to a
variety of other platforms and devices.

The initial members of the team were
Will Walmsley, Xavier Snellgrove and myself. Severin Smith joined the team
later as a co-founder. Will, Xavier, and Severin remain a core member of the
company. I've taken a step back as and I am acting as a scientific advisor to
the company. The company, in the meantime, has grown to include more
developers, designers, as well as marking, communications and business
development people.

Albrecht: Why did you go with crowdfunding? What were the
advantages for you over other funding approaches?

Khai: Of course, there is the financial benefits of crowdfunding. Because it's
obvious, it probably does not need to be discussed. But there are several other
reasons that might not be as clear, yet are important to consider.

One advantage with crowdfunding is
that it is full of people who want to support new ideas. In a sense, these are
people who are likely to be early adopters of the technology. They might be
technology savvy. And they might be people who are open to the possibility that
the product is still be refined.

A second advantage with crowdfunding
is the buzz that it provides for the product. For Minuum, while the
crowdfunding campaign occurred, the Youtube video about the product was watched
by over a million people (there were two versions of the video because the
audio in the initial version needed to be improved--the combined viewership of
the two videos went over a million in a few weeks). This helped to advertise
the product. The media also caught wind of the campaign and helped to promote
awareness about the product because of the crowdfunding effort as well.

I think the final advantage is that
it provides a way for gaining feedback about the product/idea from the
potential users while the development of the product is still occurring. That
can help to shape the product.

Albrecht: Can you give a short overview of your timeline … from
idea, to running the indiegogo campaign, to delivering the final products?

Khai: The timeline actually started well before the campaign. For Minuum, the
timeline might be somewhat unique as well. But the timeline went like
this.

I taught an HCI course that Will
Walmsley took. For the course, students were asked to develop and evaluate an
"eyes-free typing method." Will and his project team worked on a
rotational gesture-based keyboard. The basic premise of the keyboard is that
the user holds the phone in their hand. The user rotates their wrist along the
forearm's axis to select letters (arranged alphabetically), and taps the screen
to type that letter. As you can imagine, it's hard to imagine the user being
able to easily and accurately selecting a letter in this way. He and his team
designed and developed a rough prototype which demonstrated that with a
disambiguation engine behind it, it was possible to handle the imprecisions
(i.e., errors) involved with being able to correctly select letters using wrist
rotations.

The technique was interesting enough
that Will and I continued to work on it as a research project. Over this period
of time, we brought on another student in the lab (Xavier Snellgrove). Using an
iterative design process over the course of a year, we continued to develop,
evaluate and refine the prototype in numerous ways, including: dramatically
improving the disambiguation algorithm, supporting more input gestures,
providing auditory feedback and minimal visual feedback, and using two
different alphabet layouts (a layout which adapted the familiar
"QWERTY" layout to a single dimension and an expert/optimal
"ENBUD" layout). The research was published in a TOCHI 2014 paper,
but the interesting things that we learned were people could learn to use the
method to perform eyes-free typing and that users were able to use the QWERTY
layout to achieve comparable input rates to the optimal ENBUD layout (thus, the
user's familiarity with QWERTY could be leveraged rather than requiring
the user to learn a completely new layout).

The point of explaining the above is
to provide some context for what happens next.

Once we completed the Rotext
prototype, we thought it was an interesting eyes-free typing method and thought
about turning it into a product. Will was still a Master's student (and
furthermore, he was not my Masters student) and needed to finish his Master's
degree. I was also going to do my sabbatical leave at UC Irvine. So while we
were interested in commercializing, we decided to wait until he finished his
Master's before proceeding. However, when I started my sabbatical, I was
contacted by the partnership office at University of Toronto. I was told that
the university was starting a program to help incubate and commercialize early
stage technology that summer. They were interested in supporting one of my
projects.

This lead me to have a conversation
with Will about whether he would be interested in going forward with
commercializing, what we would commercialize, and what our timeline would be
like. While we thought eyes-free typing was interesting, we felt that it would
be a hard interaction method for many people to be able to learn and adopt. We
felt that the most interesting part of the work was the disambiguation engine's
ability to support imprecise typing. Furthermore, we felt that the
disambiguation engine could be used to support typing along any one dimensional
axis. I had also attempted another startup a few years earlier on the 1Line
Keyboard (a concept that we studied in a UIST 2009 paper). While that startup
effort was not nearly as successful, I had stumbled into an interesting user
problem: how to give the user more screenspace while typing. We targetted the
tablet platform with the 1Line keyboard, which was only still growing at the
time. So as a result, the 1Line company never picked up the momentum we had
hoped for it. However, Will and I thought that the concept of using his
disambiguation engine on a reduced size keyboard be really useful for mobile
phones, which has a very small screen and so any added screen space we could
give back to the applications in use would be really valuable. We decided
to call the product Minuum - because we were designing a mini sized keyboard
with keys laid along a single continuum. We also felt that this keyboard could
be the product that helps users become familiar to concept of imprecise typing
along a single axis, and then they could adapt and transition that typing
practice over to other devices/platforms/form factors (such as, typing on a
small watch or gesture-based typing like the Rotext work).

We entered the UTEST program that
summer to begin designing the Minuum keyboard. Over the course of the
summer, Will and I developed and refined our concepts for the Minuum keyboard
and the SDK which would allow us and other developers to use the engine to
support imprecise 1-dimensional typing on other devices/platforms/form factors.
It was over the summer that we started to think about crowdfunding as the way
to launch the product and bring awareness to the product and the company. Will
and I started some high-level plans about what the crowdfunding campaign might
involve, but it wasn't until we had the prototype that details of the
crowdfunding effort was thought out more.

One of the reasons why we decided to
go with crowdfunding was because the UTEST program gave us some initial funding
to help us pay Will for the summer and fall. This meant that we could afford to
ask for not a huge amount of money from the crowdfunding campaign to complete
the product. So basically we were working in stealth mode the summer and fall
of that year. We spent a significant amount of time on the keyboard design, the
various features we were going to support. Will then started to port the engine
so that it works on a number of platforms (including Android) and I developed
the Android input method. By the end of the year we had a mostly demonstrable
prototype. It wasn't a finished product, but it was close enough and
became the premise for what we showed in the crowdfuding video. When the next
year rolled around, I had returned to Toronto. Xavier had joined the team and
they worked on the launch.

We had to start to put together a
website, develop the concept video, bring on people to help with marketing and
communications (press releases, etc). I remember we had set the launch date to
be early in the year, but we ended up delaying it because getting all these
materials ready took a significant effort. Just to give you an example, the
video wasn't finished until the early morning of the day of the launch. We
still ended up needing to update the audio track in the video to make it easier
to comprehend a day or two after the launch. We ended up launching mid
March (instead of earlier) and the campaign ran for a month.

With the launch came a lot of press
and a number of people/companies contacting us. While Will and the team took
all the press requests, feedback about the idea was also coming in. This really
helped to provide an understanding of what people liked and wanted/asked for,
etc.

What's involved in releasing a
product is making the software/system run robustly. This is quite different from
creating a research prototype. Coding and testing of the product, tracking of
bugs, etc. is quite important and requires a lot of resources (including time).
So while it seemed like a lot of time often goes by before a
product actually gets released after we hear about it initially, it's
primarily because taking it from a concept/research prototype to a deliverable
product still requires a significant amount of development/testing/debugging.
For us, the beta version was release June of that year (or about 3 months after
the launch).

The team has gone onto participating
in the Y Combinator accelerator program and grown in size some (adding
developers). They've developed an iPhone version of the keyboard. They've
developed smartwatch versions of the system demonstrated additional
experimental uses of the SDK (such as Glass typing, or typing using a remote
control, or a leap motion device, etc.). They've done a marvelous job of
growing the company and the product in exciting ways. More information about
all of these different efforts can be found: http://minuum.com/mediaroom/ .

Albrecht: With crowdfunding you have customers for a product
often already at the idea stage. How does this impact the product development
and the final implementation?

Khai: User feedback at any stage of development is always valuable. The most
important one that crowdfunding provides is whether potential users find the
overall concept appealing or not. Different from traditional product
development, where we might have fully built the product, then try to put it on
the market and see if people *might* buy the product, crowdfunding allows for
companies to get insight into whether such customers exist already.

During the campaign, funders will
discuss features that they are excited about and what they want and hope to
have included in the product. The funders also get early access to the
product (the beta version). This provides them with the opportunity to give
us additional feedback before the first non-beta version is completed. All of
this information helps us to understand user requirements and prioritize
features. Obviously, not everything can be included in the initial version that
gets released, but we can develop a list of features that gets added to
subsequent versions.

Albrecht: You funded the development of software. In your
research you created typical ubicomp systems – what challenges do you see in
using crowd funding for ubicomp products that include hardware and software?

Khai: This is a really interesting question. Minuum was primarily a software
product, which has very different costs to a hardware product. In particular,
producing hardware in certain volume changes the costs involved. The same is
not true with software.

So in a sense, funding the
development of a hardware product is more difficult. But what I think
crowdfunding does for the funding of a product that includes a hardware
component is that it mitigates some of the expense incurred for initially
producing at smaller volumes. What makes it hard for a company, when
hardware is involved, is that the manufacturing of a large amount of their
product might not be wise early on. The challenge is then of course the
pricing associated with the product, and what to ask from crowdfunders so that
it seems reasonable.

Albrecht: How is crowdfunding changing how we make ubiquitous computing
products? Are there new classes of products that become economically viable?

Khai: I think crowdfunding allows for us to take concepts that we have done
some basic research and development on, and turn into actual products when
previously we would need to secure the funds to do so first. Even if we know
that an idea can work and can be turned into a product, can we find people who
believe in us enough to fund that development? Crowdfunding allows for enough
people who believe in the idea to share some of that cost.

Ultimately, I think this can benefit
ubicomp products that have some hardware component. The cost to create that
product is high. We can show people large bulky prototypes of the same concept,
but would a large bulky prototype be enough to convince an investor to provide
the significant funding needed for the development of that product? Maybe, if
they could be convinced that there is a particularly large market for the
finished product. And that's what I envision crowdfunding doing, it helps to
incur some of that cost. It helps to demonstrate market size. And this helps
the company grow and develop the products enough so that they can reach the
final design, price point, experience etc. that would be otherwise hard to
achieve for their product.

Albrecht: With crowdfunding you give your idea away (or at
least you make it public) before you can deliver it. Were you afraid of others
being faster in creating "your" product and having it on the market
first? Did you take precautions to avoid competition?

Khai: We had patents filed already before the launch.

We also didn't want to overpromise
and not be able to deliver as well. So we had many of the capabilities and much
of the backend for the product created already. They were not fully tested.
They didn't do everything the released version supported, and they didn't do
everything that is supported in subsequent versions either. But enough of it
was completed that we knew a) we could do it, and b) we were "months"
away from an actual release. That would make it hard for others to catch up.

Short bio:
Khai N. Truong,
Ph.D. is a professor at the University of Toronto. His research lies at the
intersection of Human-Computer Interaction (HCI) and Ubiquitous Computing
(UbiComp), specifically examining the mutual impact of usability and technical
constraints on the design of applications and interaction techniques for novel,
off-the-desktop computing systems that may be commonplace in 5-10 years. He
received his PhD in computer science from the Georgia Institute of Technology.

If you plan to obtain the most efficient and rewarding crowdfunding PR that will allow you to definitely get the money you'll need, we merely are not able to help but highly recommend you proceed to the crowdfundbuzz.com