Yesterday Paul Graham posted an essay about Apple and the iPhone dev process, along with a new Request for Startup (RFS). It’s a good read, and one of the hypothesis put forth is that developers will write software for the device that they have.  Many developers have iPhone, and therefore are targeting the iPhone for development.  As a result, one way to woo developers away from the iPhone ecosystem is to create a killer app for developers, and suggests that one such app may be an environment that allows developers to write code on mobile devices.

It’s good timing from my perspective.  I’ve been away all week in LA at Microsoft’s Professional Developer Conference (PDC) and have been immersed in dev content.  I love events like this because being surrounded by smart people and new concepts helps to stimulate my own thinking.

When thinking about mobile development, there are a few assumptions that I’m going to put forth to differentiate between a traditional IDE:

• Extremely limited screen size
• Cumbersome to enter text
• Low client-side processing power

Of course, you could just get around these constraints by connecting to a mouse, keyboard, and monitor – but that’s kinda boring, so I’m going to focus on a scenario that assumes no access to peripherals.

OK,  now let’s start to narrow it down a bit.  First, let’s focus only on building mobile apps.  There’s no reason why you couldn’t spread to web apps, but mobile apps make sense because you’re already on the device itself, which gives you a slight advantage due to the WISIWYG-iness of it all.

To start looking at how this would work, let’s walk through a simple scenario and start explaining some of the details as we go.  Since I’m typing this up in the airport waiting for updates on my delayed plane to arrive (I heart LAX!), let’s say that you wanted to build an app to track the status of a specific flight. 

To get started, the first thing a dev would do is to create a high-level model of the app.  This would be a simple block diagram that would start by walking through the UI flow of the app.  Once you had each block in place, you would drill into each block and define the type of functionality you want for each step.  For example, your first screen might be a splash screen with your logo.  Next would be a form that would let you enter your flight information, followed by a third page that would display the status.

Each block would be driven by customizable templates.  There would be 100’s of pre-built templates available from the system, and also the option to pull in user-generated templates from the community.  For our example, the first block would be a “Splash Screen” template.  Once you choose the template, you then walk through a simple wizard to modify the template.  Again, for this example, the wizard would ask for the image that you would want displayed on the splash screen.  When you’re finished, the system would do all the work on the back end to turn it into a fully-functioning splash screen for your app.

Once you have the UI elements in place, it’s time to start wiring up the back end.  This would be done using a similar model-based approach to build out a high-level abstraction of the program’s functionality.  For example, let’s look at the input form for the flight tracking example.  The logic flow is roughly something like this:

1. Get the airport code for the user’s starting and ending destination
2. Hit a web service to look for all flights to/from those locations over the next 12 hours
3. If there are multiple flights, let the user pick the correct flight
4. Send the flight info to a web service and pull back the flight status
5. Pass the flight status to the display page and give up control

One of the keys to making this work is to rely very heavily on the ability to package up very common mobile development tasks into small snippets of code.  As devs work through the logic for their app, the goal is to break down the elements of work into smaller and smaller pieces until you get down to something that can be represented by a short, common snippet of code. 

Of course, the code could be modified once it’s in place, but by starting with a rough framework, we solve two problems.  One, it would significantly reduce the amount of typing.  Two, it would enable the developer to spend more time simply modifying code instead of having to switch over to a browser to look up syntax or do a search/copy/paste.

The revenue model would be similar to Weebly, where users could build one app for free, and could build additional apps for a small fee.  Another potential revenue possibility is to automatically submit the apps to the app store and tack a small “service fee” on top of the standard submission cost. 

There’s a lot more to this idea, but this post is already getting a bit long so I’m going to call it.  To stay updated on my latest ideas, you should follow me at @astartupaday on Twitter.

<boringstoryaboutkevin>

Way, way back in the early days of my career (‘01 or so), I started an incredibly small little startup focused on building custom software for researchers.  For two years I wrote software that would track the movement of lab rats in cages for Parkinson’s researchers, which led into an opportunity to work on an insanely awesome project called the Direct Brain Interface (DBI).

The premise of the DBI was to detect patterns in the electrical activity in the brain, and use those signals to control a simple video game.  There are a few catches, though.  First, instead of using rats, the team was working with real live humans.  And second, as opposed to the Indirect Brain Interface, the signals we were reading came from probes that were inserted directly into the brain.

Like I said: insanely awesome.

Of course we didn’t insert the probes for the sake of the experiment, we worked with patients who already had the probes inserted for other medical reasons (mostly as treatment for severe epilepsy). 

Anyway, I spent the summer writing all sorts of crazy signal processing algorithms for two main purposes.  The first was to look at the signals coming in from the 30 or so probes to try to discover the location of the specific “thought” we were trying to capture (brains are crazy flexible, no two are the same).  Then, once we found the right location, we then analyzed that one channel to pick out the “thought” as it occurred.

I had never done much signal processing work before, but the amazing thing was that once you got all the wickedly complex math right, it would actually do a pretty good job of picking up a signal out of this incredibly noisy input from the probe. 

</boringstoryaboutkevin>

This is leading somewhere, I promise.

There are millions of candid photos floating around the Internets, especially as more and more people opt-in to share their Facebook data with the public.  And just like that tiny signal that could be pulled from the noisy brain probe, I believe there are lots of interesting things that could be pulled from these pictures using similar signal processing techniques. 

The one that I’m focusing on today is a site that looks at pictures of people and tries to determine the most popular clothing and fashion choices.  For example, if the algorithm found 100 pictures of people wearing the same purple-and-pink tank top from the Gap in the past 24 hours, it would show up on the site in the “Hot Now” section. Users could go to the site to see what clothes, shoes, purses, etc.. are popular today, and click through to purchase the items online from their favorite stores. 

Along with just pictures, we could also throw in a little metadata for more accuracy.  For example, if the photo is from a public Facebook feed, we can cut the data by age, location, and even popularity (measured by number of friends).  You could also use that same data to apply weighting (i.e. a purse that is worn by a college student in New York City with over 1,000 friends would get a high weighting)

The end result would be a constantly-updated site showing the hottest fashion styles in real time.  Think of it as a Digg for fashion, but one that doesn’t have the wicked-hard chicken/egg problem of getting users to contribute content to an unknown site.  Along with generating money via lead-gens to online stores, the data could be used to generate real-time reports for fashion designers. 

Like this idea?  If so, you should follow me on Twitter at @astartupaday. 

If not, you should probably follow someone else.

If you’re reading this blog, chances are that you’ve at least heard of Y Combinator and the community over at Hacker News.  If not, stop reading immediately and go check those those sites out.  There’s a lot of good content on the web, but these sites are consistently churning out some of the most thoughtful and interesting stuff around. 

Last year I did a series of 30 posts centered around a list of 30 startup ideas that Y Combinator published as a creative starting point for applicants to the YC program.  This year, they took a bit of a different approach by posting only a handful of ideas, but with much more detail.  Today I’m going to take on the first one, which is called “Future of Journalism”:

Newspapers and magazines are in trouble. We think they will mostly die, because we think we know what will replace them, and it is too far from their current model for them to reach it in time.

And yet people still need at least some of what they do. You can’t have aggregators without content. So what will the content site of the future look like? And how will you make money from it? These questions turn out to be very closely related. Just as they were for print media, initially. The reason newspapers and magazines are dying is that what they do is no longer related to how they make money from it. In fact, most journalists probably don’t even realize that the definition of journalism they take for granted was not something that sprang fully-formed from the head of Zeus, but is rather a direct though somewhat atrophied consequence of a very successful 20th century business model.

What would a content site look like if you started from how to make money—as print media once did—instead of taking a particular form of journalism as a given and treating how to make money from it as an afterthought?

(The good news is, we think the writing will actually end up being better.)

Groups applying to work on this idea should include at least one person who can write well and rapidly about any topic, one or more programmers who are good at statistics, data mining, and making sites scale, and someone who’s reasonably competent at graphic design. These functions can of course be combined, and in fact it’s even better if they are. Ex-Googlers would be particularly well suited to this project.

For those of you who didn’t read my ideas from yesterday and Friday, I posted some thoughts around a site that generates real-time, user-curated content, and an ad model that is optimized for ads that appear on real-time content.

Those two ideas actually started out from this post about the “Future of Journalism”, but it ran so freakin’ long that I decided to break it out into two separate posts so I’d have more room to explain them both.  So, looking at the RFS, I started with this line:

What would a content site look like if you started from how to make money—as print media once did—instead of taking a particular form of journalism as a given and treating how to make money from it as an afterthought?

The revenue model I came up with is the Real-Time Ads model, where users could instantly bid to have their message (commercial or not) appear on the page.  Now, in order for this to work, you need to have a whole heck of a lot of real-time content.  That’s where the Real-Time Content (or Qwiki) idea comes in.  This would be a content site that scans for the latest Twitter trends and automatically creates a basic page about the topic, which users can add to over time. 

Bring these two ideas together, and you’ve got my answer for how to take on RFS #1: Future of Journalism.

What do you guys think about this one?  As always, if you want to stay updated on my latest ideas, you should follow me on Twitter at @astartupaday.

I think it’s safe to say that advertising has advanced quite a bit in the past fifty years.  It’s an interesting field because it’s such an incredibly big market ($350 billion worldwide, and growing fast) that the opportunities for disruption are huge, which historically has led to a ton of innovation in the space centered around major inflection points in the way we consume information. 

From print to radio, radio to TV, TV to the Internets – each has opened up massive opportunities for the companies that have unlocked the delicate balance between consumer tolerance for interruption and profitability.  Looking at the market today, I see a big inflection point around the shift from the traditional web and the real-time web.  There are lots of players in this space, but we have yet to see a breakout advertising platform to find that balance and cash in around this major opportunities.

For today’s idea, I’m going to take a crack at this with something I’m calling Real-Time Ads.  These are ads that are optimized for type of quick-hit, real-time content that has a virally-powered explosion and quickly dies away. 

It’s a bit hard to explain, so let’s start by looking at the following scenario.  The Seattle Seahawks won a late-season game in overtime are making an improbable trip to the playoffs.   I’m a huge Seahawks fan, and after reading an article on the big win, I decide to post the following social ad on the page:

Now, let’s say that this week the Seahawks are playing the 49ers in their playoff game.  I decide that I want to have a little fun, so I head over to the 49er’s page and bid on the following ad:

The key is that anyone can click directly on the ad, and for a very nominal fee, immediately purchase the opportunity to get a targeted message in front of a massive viral audience.  Also, this is a simple way for very small businesses who don’t want to learn about traditional online advertising to instantly see their message on a site that they know is relevant to their prospective clients.

The other nice thing about these ads from a consumer’s perspective is that the ads aren’t just the same old boring AdSense ads that users have learned to ignore.  Because they are coming directly from users, they are likely more interesting and fun, which will make these not feel like ads at all to the consumer.

Here are a couple of other scenarios where social ads might come into play:

• Twitter user “@iPhoneNews” advertising on a popular article about the iPhone
• The person selling “Bubble Boy” Halloween costumes advertising on a hot story about BB.
• A pizza place in a small town offering a $5 coupon on a story about the local high-school basketball team winning their game.

All right, what do you guys think about this one?  Leave comments below or hit me up on Twitter at @astartupaday.   

As you might have guessed, I love trying out new sites that pop up on the Internets.  The vast majority I check out once, and never return.  However, the one place that I’ve been going to more and more over the past few weeks has been the new Twitter search functionality that was built into Bing. 

Full disclosure for those who don’t know – I do work at Microsoft.  But putting silly religious search engine wars aside, it is a cool service and will likely be implemented in a similar way when it rolls out to the search engine of your choice in the near future.

Anyway, it’s a very useful service and got me thinking about real-time search.  Before checking out Bing’s Twitter search, I had assumed the problem that needed to be solved was something like this: now that we now have a ton of real-time content (tweets), how do we index, weigh importance, and filter the content to discover the most interesting tweets? 

However, after seeing how much more useful Bing’s Twitter search is compared to Twitter’s built-in search, I started to look at the problem differently.  The key is that the tweets themselves aren’t the content, they are simply indicators that can help determine what links to non-Twitter content are most important for a given topic, at a given time, in a given location. 

If you look at it from that perspective, the problem is now reversed.  Instead of trying to build a real-time search engine, what about creating a real-time content engine?  That’s the basis for today’s idea, Qwiki.

Here’s how it would work.  An algorithm would monitor Twitter to determine the newly-trending topics.  Once a topic hits a certain threshold, the Qwiki site generates a web page for that topic with as much information as it can automatically pull from both Twitter and the web.

Qwiki would then tweet out a link about that topic.  As people come to the Qwiki site, they could start to fill out information about the topic, and retweet the link out to others.  As more and more people come to the page and contribute information in real time, the wisdom of the crowds will take over and page will quickly become the best source of information about that topic.

As a result, just as Wikipedia is one of the top entries on most search engine queries, Qwiki results could rise to the top of real-time search requests.  And while I usually don’t like ad-based revenue models, it might actually make sense for this one – especially if location-based, real-time advertising begins to take hold.     

Speaking of real-time, I’m in Mountain View today and will be working out of Red Rock Cafe from about noon to 2:30.  If you’re in the area, swing by and I’d be happy to buy you a coffee.  I’ll be on Twitter, you can contact me there at @astartupaday. 

Each night before I go to bed, I check in on Hacker News to get a brain dump of  the latest Internet geekery.  The last story I read before drifting off was a fun post by John Skeet titled “OMG Ponies!!! (Aka Humanity: Epic Fail)”.  And when I woke up this morning, I was pleasantly surprised to find a fully-formed startup idea in my head.

I’ve been really good lately about having concrete ideas based on solid business rationale.  So was it about a new idea in the financial services space, or a killer take on the mortgage sector?

Nope.  Unfortunately, it was this:  “OMG!  Ponies!”

Thanks, Jon.

Today’s idea is a social game called “OMG! Ponies!”.  The premise is as follows: A new Facebook poll indicated that ponies had dropped from first all the way down to eighth on the “World’s Cutest Stuff” list.  Understandably, the world pony population was pissed, and is now exacting revenge by seeking to eradicate each of the top seven cute items on the list.

Your job, as commander of an elite group of pony assassins, is to prep your squadron for an epic cute-on-cute battle for world domination.  Train your pony in mixed martial arts to take on the Fluffy Bunny in the Octagon.  Earn enough money to buy a blowtorch for your showdown against the Teddy Bear.  Gather your friends and level up your squad for the final fight: a wicked chainsaw melee against the Magical Crying Unicorn.

The game play would be  similar to other social games on Facebook, such as Farmville.  Players work to level up their character to unlock new challenges, and can earn (or buy) in-game currencies to purchase new weapons.  Users can team up with their friends to build bigger squads.  It’s sort of like Mafia Wars, except replace “violent gang banger” with “adorably precious pony”.

Despite the initial WTF element of this idea, I do actually think there is some merit here.  The game would have a mixture of humor and violence, which are two good elements of a successful viral social game.  Plus, the uniqueness of the idea would be enough to get an initial kick start of buzz.  Finally, now that Facebook is flooded with overly cheery, cute cartoony apps, this could capitalize on the counter-culture app backlash that is almost certain to materialize.

I’d definitely love to hear your comments on this one.  And if you’re not already, you should follow me on Twitter at @astartupaday.

Like playing Skate or Die on a Commodore 64, redialing the modem to get connected to AOL’s perpetually busy servers, or writing a crappy RPG in QBasic, getting braces is a rite of passage in any young geek’s life. 

I hated it at the time, but looking back I’m so incredibly grateful that my mom scraped together the money to pay for three years of orthodontic work.  Man, those suckers are expensive!  But expensive, one-time purchases, as I noted in yesterday’s post, have great potential to be a solid niche in which to build a lucrative online business.

Today’s idea is deceptively simple – a site where people can upload a picture of their teeth and get recommendations from local orthodontists on whether or not they need braces. 

The key to this idea is that it is a win for both sides.  People who think they may need braces get feedback from real professionals without having to leave the house.  You could take a quick photo from your webcam or phone, throw it up on the site, and specify the type of insurance you have.  Within minutes, you could be getting Emails or messages back directly from orthodontists that are covered under your health plan. 

From the other end, orthodontists receive very well qualified leads from potential patients.  Instead of a lead coming in as just an Email address or a click from an online ad, the orthodontist can tell at a glance whether or not the person in the photo is ready for braces along with the relative complexity of the situation.

Another niche idea – what do you guys think of these?  To stay up-to-date on my ideas, you should follow me on Twitter at @astartupaday.

You wouldn’t know it based on the sissified city-boy that I’ve evolved into over the past 10 years, but I actually grew up on a small farm in the palm of Michigan.  I have a soft spot in my heart for the country, and I’m eagerly awaiting the day when I can trade in traffic jams and lattes for unplowed dirt roads and warm milk from our old brahman Bessie.

For today’s idea, I’m taking a bit of a departure from my usual shtick.  Instead of coming up with some random idea and tacking a business model onto it, I’m starting by looking at a potentially profitable niche and thinking through ideas that could serve the target audience.  The niche I’m exploring today is Agricultural Equipment.  It’s a big business (John Deere alone rakes in over $25 billion in revenue), and with equipment costs that can easily exceed $100,000, there’s a nice business to be had for generating qualified leads for farm equipment retailers. 

In thinking about this market, I was reminded of a fantastic speech I heard recently by Rich Barton, founder of Expedia.com and CEO of Zillow.  In the speech, Rich said one of the secrets to his success was to empower the average user with information.  He then took on markets with high-cost purchases (flights, vacation packages, houses) and built a site to help the average consumer use the available data to make an informed decision.

So, for used farm equipment, my idea is a site called “Harvestimates” which allows farmers to enter in basic details about their equipment and get back an estimate of what it’s worth.  Each month, an Email would be sent to the farmer informing them of the updated value of all their equipment, provide options for users to sell their equipment online, and show options to upgrade their equipment or purchase new accessories.

What do you think of this one?  Would you bet the farm on this one, or am I counting my chickens before they hatch?  To stay updated on the latest posts, you should follow me on Twitter here.

I wanted to post a nice Web 2.0 Halloween pic today, maybe a Fail Whale carved into a pumpkin or two people dressed up as Steve Jobs and Bill Gates as conjoined twins.  But I just couldn’t find the right one, so I went with the old timey witch instead. If you know of a good one, shoot me a link in the comments.

Speaking of, have you seen the “GuyPhone” costumes?  Nice.

Yesterday I officially announced my return to blogging (thanks for the nice reception, btw – it’s on track to be my most viewed post ever!) and today I wanted to follow up with a quick meta-post about what I have planned for the new and (hopefully) improved ASAD.

First, I’m still going to pack in as many run-on sentences as humanly possible.

Second, I’m really going to try hard to stick to a more regular posting schedule.  I purposefully picked the name “A Startup A Day” for a reason – to put myself on the hook to post on a daily basis.  While life may interfere on occasion, I’m shooting to post every Monday – Thursday, set to auto-publish at noon.

Third, I’m going to alter the content a bit.  Historically, I’ve been pretty strict about only posting startup ideas, no commentary, navel-gazing, or other fluffy stuff like that.  The majority of posts will still be ideas, but I’ll probably put up a few essays or other thoughts from time to time.  Hopefully it will liven up the blog a bit, both for you and (more importantly) for me. 

And finally, the ideas themselves.  This economic shake-down has led a lot of people to rethink the old model of building a web-based startup, where “old model” =

1) Build a website

2) …

3) Profit!

Previously, a lot of my ideas were something that sounded vaguely cool or useful, with a business model duct-taped on as an afterthought.  Instead, I’ll be trying out a new ideation process of starting with the business model, and building the idea around it.

Oh yeah, and one last thing.  In the nearly three years since I’ve had this site, I’ve always resisted plastering my site with ads or anything like that.  No offense to anyone who runs ads, but I just fell it makes non-commercial sites like this feel kinda tacky, and my readership is so small that it’s just not worth it.  But, more for the sake of experimentation than anything else, I might start playing around with some tasteful ways of monetization.  I’ve got a few ideas, but if you’ve seen something work well for a small hobby blog like this, please let me know.

I’m pretty excited to start this thing back up again, and I sincerely hope you like the new approach.  Feedback is always, always, always welcome – post ‘em if you’ve got ‘em.

Back in June, I made the decision to break up with WordPress and post all my new startup ideas to Twitter.  Six months later, I’m walking out on Twitter and returning home to my blog. 

Why?

Like any fling, at first it seemed like a match made in heaven.  To heck with all these “words” and “thinking” – with Twitter I could just dash off a few keystrokes and I was done.  Twitter fed my innate predisposition towards habitual laziness and instant gratification. And for a while, it was pure bliss.

But like taking a leggy blonde wearing three inch heels on a hiking trip, the practicalities of the situation soon begin to set in.

Shoehorning my ideas into that 140 character box required me to cut out features, water down the functionality, and strip out all of my color commentary (which may not be such a bad thing for many of you).

For example, take this one (from mid-July of this year):

Idea: OneClick – Mobile app, allows users to perform commonly-used, very specific actions in a single click.(i.e. get directions to address)

Now, in my head I was thinking of something like AppBox Pro, which released in September and has been comfortably perched in the top 50 paid apps list ever since.  If I had more room, maybe I would have gotten the chance to really sell this vision and possibly even given one of you the inspiration to build something like this yourself.  But, instead, I just dashed out the idea in a minute or so and went back to checking myself in the mirror to see if there was any lipstick on my teeth.

As I alluded to in the title, I don’t mean for this to be an indictment of Twitter.  I’m still going to be using it regularly for quick status updates or to notify followers when I have a new blog post ready.  Like most shiny new things on the Interwebs, it’s all about finding the right tools for the job at hand.

So, what’s next for the blog? 

First, I’ve got a handful of Twitter ideas that I’d like to flesh out a bit.  Also, my old buddy Paul Graham has posted a few more idea stubs that I want to tackle.  I’ll keep doing more of the same ol’ post-an-idea shtick, but I may try to experiment with more practical ideas along with the crazy ones.  

And finally…I know it’s against everything that is good and holy in my world, but I’ve actually taken a few trips outside of my ivory idea tower and started coding again. 

Thanks for reading, and, Twitter?  Keep your chin up, kid.  I know it hurts now, but I have a feeling you’re going to be just fine.