Outer Thoughts » Ideas

Talk me through the menu – recipe app idea

arafalov — Sun, 03 Jul 2011 22:14:47 +0000

Recipe and cooking apps are aplenty, but it is hard to use an app while cooking and having wet or dirty hands. This may not be a big deal to experienced cooks, but for the beginners it is a catch 22. They want to follow the recipe, but get lost between steps, timing and multiple things that sometimes need to happen in parallel. Technology to the rescue.

Imagine a pasta cooking application on an iPhone. You pick a recipe, chose how soft you would like it and what sauce you would like to make for the pasta. Finally, before you start, you put your Bluetooth headset in and say “Start”. Application, recognizes the key phrase and starts walking you through the recipe. The sequence will – roughly - look something like this:

(App): Put the water to high-heat and add salt to it. When ready, say “Next”
(Cook): Does the steps, says “Next”
(App): Now that we are waiting for water to boil, let’s start cooking sauce. If the water boils, please say “Boiled”.
(App): Let’s start with the sauce, please collect X, Y and Z ingredients together; when you are ready, say “Chop”.
(App, 5 minutes later): How is pasta water going, remember to say “Boiled” when it is boiling.
(Cook): “Boiled”
(App): Great, now let’s add pasta slowly; when done say “Cooking”
(Cook): Adds the pasta, says “Cooking”
(App): Great, we now have about 10 minutes, let’s continue with our sauce, you were doing Step C
….
(App, 8 minutes later): In about two meetings it might be a good time to check on pasta, I’ll remind you then.
(App, another 2 minutes later): Let’s look at that pasta. Pull out a piece and bite it. Say “Ready” if it feels just chewy enough, otherwise say “More cooking”
(Cook): “More cooking”
(App): No worries, let’s finish off the sauce while we wait for the pasta.
……

The basic idea is simple, let the application walk you through the instructions and voice recognition to control it. Bluetooth headset means the interaction can happen without having to switch between the cooking and looking the steps up, though of course the current step(s) can also be displayed on the screen. To keep things interesting, the app can also play music or tell little stories about ingredients.

Enough for the idea, now let’s think about making it a viable application people would pay money for:

Let’s start with a free application that has 3 starter dishes that can be prepared separately, but will demonstrate the parallel-cooking capability if prepared together as a full meal. The free app will mean more people will try it out, thus driving the visibility.
Now that people can see the app’s benefit, they can buy sets of recipes using in-app purchase. The sets can be based on style (Italian, Thai, Japanese), theme (Xmas, Thanksgiving), time of day (Breakfast, Lunch, Dinner) or dietary requirements (Atkins, vegan, South Beach).
In addition to the recipe purchases, there could be a Pro version. One feature would then be asking how many burners are available and optimizing for that. Another feature would offer ingredient substitution.

This gives us a core behavior, but the apps work best if they have some sort of engagement/gamification built-in. Let’s see what experiences we can add outside of kitchen time:

A successful application will have new recipes issued (programmed/voiced) over time. Let’s allow people who are using applications to vote on which recipes should be made available next. And to drive users to the application, this voting can only be done inside the application, though the results should be show on the application’s website. This specifically means that recipes can be voiced just in time based on the demand and voting results.
To encourage voting, give away a small number of winning recipes to the people who voted for them, either randomly or for the first person to vote the recipe up.
Similarly, allow people to vote on how difficult a particular recipe is, how much they like it and other normal features found on the recipe websites.
The gamification principles would obviously give us a score board for cook-offs where friends could try a particularly challenging recipe or reward points/badges for doing a recipe or progressing from easy to hard recipes.

Not all the money has to come from the end users. Once enough people download the application, the usual cross-promotion and third-party revenue streams become viable:

An application can offer sponsored recipes for free (“Brought to you by X”).
Recipes may use using product placements (“Brand X sweet chile sauce”)
Affiliate and referral fees can be earned by creating ingredients packages and sending the users to online-shops to buy them
Finally, white-label services can be offered to other recipe magazines or books to show off several of their recipes and drive people to buy the full book/magazine

We know such an application is possible. Now somebody just needs to make it real.

Say your name – idea for podcasters

arafalov — Mon, 20 Jun 2011 03:11:41 +0000

I listen to a lot of podcasts on many different topics. Most of them have nothing in common – except for one thing: they butcher the names of people (cough JavaPosse cough) Those mispronounced names could be of people sending comments, of known people in the community or just some other strangers.

Seems like it would be a valuable service to have a website that people could record their names on. Given that most the podcast speakers know the people to be mentioned one way or another, it would not be to difficult to send them an email request to hit a website that allows to record that name. Then, every time they need to pronounce the name, they could consult the website and save the time to all the listeners with bad attempts and apologies.

And if the website allowed for the name to be embedded in a website as a widget, this could even be a part of people’s calling card to embed their own name on their website. There might even be synergies with identity services such as LinkedIn by exposing person’s name’s pronunciation as a widget on their profile.

The problem of course is how to monetize such a service. Even with short snippets required to deliver the audio for the names, it would add up if the site became popular.

Still, obviously some people think it is worthwhile doing (as a hobby). A search to see if such service already exists turned up a couple of sites:

None did exactly what is actually needed for the podcasts, but something is better than nothing, right? And they did well enough to be mentioned in newspapers or even on TV. Must be something in this idea after all.

Where are all legal computational linguistics resources?

arafalov — Wed, 14 Jan 2009 01:41:44 +0000

I am frustrated. I know my corpus (resolutions of the United Nations General Assembly) shares a lot in common with biomedical and legal domain. And I can find interesting articles in biomedical domain dealing with similar issues of complex tokenization, long named entity mentions (though mine are much longer), etc. But I see nothing in legal domain.

I have just gone through all of Jurix‘ proceedings as well as all of Artificial Intelligence and Law and all I got is between 2 and 4 articles worth following-up.

There must be somebody actually trying to parse real legal texts and figuring out to deal with complex organisation, people and group names. But all I can see is articles dealing with levels from ontology and up.

There might even be money in it!

One of the crazy business ideas I had was to parse all the web-based terms of use and privacy notices and annotate/crowd-vote them for how bad they are. So, before creating a web-based account, I could check it against database/parser and it would highlight and rate for me passages that I really should pay attention to (e.g. we sell your contact details to every spammer we know ). Since the language of those notices is often ritualistically formulaic, extracting interesting and useful summary would actually be simpler than it looks.

And the business model would center on providing automatic notification option if a notice from subscribed website sneakily changed and became much worse. That way one would pay money for peace of mind that there were no unexpected service rule changes.

Viewfinder Friends – idea for Facebook application

arafalov — Wed, 14 Nov 2007 14:37:16 +0000

Use case

Photos are inherently-social event markers. We take pictures to remember an occasion and – often – people who were present with us at that point. While most of the photographs are not looked at more than once or twice, the more popular ones become very important in our history.

The same does not happen to other people on our photograph, despite our best efforts to share. Emailing photos is cumbersome and subscribing to Flickr streams requires all people to look at all photos just in case they are in it.

Once upon a time, Riya.com got a lot of attention for promising to fix that. You would upload your photographs to Riya, train it to recognise your friends and family and it would then automatically find those people in newer uploaded photographs and notify them. Riya even had a basic Social Network, so the photos could be tagged collaboratively.

Eventually, Riya has failed and changed focus to become just another Visual Search Engine. I suspect at least part of the downfall was the single-purpose destination of Riya. You had to register, upload photos, train application, invite other people and do many other basic things with fairly small return on such investment of time. It was much easier to just dump photos on Flickr and let others make an effort of subscribing to your feeds.

Enter the Facebook. It is extremely popular, has all the machinery for registration, adding friends and photos and provides free development API. As it is a platform, rather than a single-purpose destination, it is more sticky than, say, LinkedIn. Succeeding as an application inside Facebook can bring more than a million people to your application.

There are many photo related applications inside Facebook now; more than 400 at the latest count. Most of them however are fairly basic. Combining computationally interesting idea with distribution platform of Facebook could be a wining combination.

Basic business flow

You receive a message from Viewfinder Friends Facebook application that somebody in your network has a public photo with you on it. You can install the application to see which particular photo was tagged for you. That’s the viral distribution method, that most of Facebook applications rely on.
Interested, you add the application. At that point, it shows you the photos from your friend’s profile that he/she has marked with your name. It also presents your photographs and asks you to name people in them. The lookup is all inline and the facebook names are automatically auto-completed, so it does not take much time. The application now spreads to the other friends you nominated.
After a while you come back to your profile and there is another picture with you in it from a friend using the application to tag you. That means he/she have thought of you. Delighted, you keep the Viewfinder Friends in hopes for future signs of attention. The aperiodic, but obviously personal nature of the gift makes the application sticky.
The application does not just show the pictures, it recognises where the people on the photograph are and asks to actually map people’s names to their faces. The mapping can be done by you or by your friends that you identified as being in the picture, but are not yet matched to the face. The distributed marking effort makes the application more interesting and easy to use.
Mapping faces to names also allows to train the application on facial recognition (Riya’s original promise) and later to automatically guess the names of people that the photograph show. Automatic people recognition will increase return on time investment and will make application more sticky. It will also make the application more viral, as knowing that all but one of the faces are identified and have the application installed, increases the pressure on the remaining people to join the Facebook and install the application.

Revenue

You take a picture of a friend at a party, waving a can of beer at you. You upload it to your Facebook account and mark it with your friend’s name (say Kevin). Viewfinder Friends pipes up and mentions that the beer in the picture of Kevin is actually delicious Busch Light and there is currently a taste promotion on it run by the distributor in your area. A link is provided to request a free sample.
This information can appear either as application notification, or as a different-color box on the picture. It could show up to you only, to Kevin or to anybody who can see the application. Either way, this is an advertisement that is strongly targeted and is in context. The cost per click (or per transaction) of such advertisements is much higher than for average banner ads.
You go skiing on a weekend and there is a notice at the hotel saying that if you take a picture of the hotel’s front and upload it to Facebook with Viewfinder Friends application installed, you will receive a personal discount of 15% next time you come and stay at the hotel. Happily, you take a picture of yourself, still red-cheeked from skiing, goofing around in front of the hotel with your best buddies. The application recognises the hotel name (or Data Matrix element) from the picture and messages you and everybody else you identified in the picture the discount code. The advertisement costs nothing to the company beyond the initial setup, is created by happy visitors and is shown to other people in context of the trip. The impact of such an advertisement would be much higher than a stock message.

Implementation

Joyent can provide Facebook hosting that scales up or down depending on demand, making it cheaper to build out the infrastructure. Currently, they even offer some free Facebook application hosting and bandwidth to the limited number of developers.
Initial fund for the business can come from one of many Facebook specific funds. The facial recognition part does not have to be implemented until after the application has proven itself popular.

“Your local friend” – business idea for travellers

arafalov — Thu, 04 Oct 2007 15:16:08 +0000

Use case

Many people come to the foreign countries and feel lost/confused traveling around and/or getting services. If possible, they like to go places with a local friend who will point out the best features, explain how things work and/or translate the requests into the local language. This is a service for those who do not have such a friend.

Basic business flow

A service kiosk in the airport (visitor’s center) would hire out he mobile phones with GPS/Camera built-in. A visitor picks up the phone and gives his language preferences.
At any point, the visitor can call the local service number on speed-dial and they will be helped with services that voice+GPS+SMS+Camera can do. For example:
1. The agent answers the call in visitor’s language and can translate the communication between the visitor and locals (via speaker phone). If it is a sign, poster or written material, it can be photographed and sent to agent for explanation.
2. The agent knows where the user is located (via GPS) and has internet access to street directories, toilet maps, phone directories, public transport, traffic maps, Google Earth view, local rules, etc.
Therefore the agent can advise the visitor on any issues that visitor needs resolved (in their language). Any notes can be sent via SMS to ensure understanding/recall.

Additional features and up-sell opportunities

If the visitor brought their different-standard phone over, use the service interface to automatically copy the phone numbers onto the new handset with automatic cheap rates via (for example) Rebtel number substitution. Or phone/Skype integration.
Provide alarm, booking, etc services
Provide audio tours via integration with GPS and IVR system
If the visitor provides their social network credentials, integrate with those systems to post sent geocoded pictures to user’s account and/or provide two-way integration between SMS and Skype
Provide language lessons (speed dial 8 for the “target language” taught by “your language” tutor)
The service can be pitched as for emergency use only, so that the fee for hiring the phone without actually using it would be similar to car insurance (couple of dollars per day).

Revenue

The revenue would come from charging for the services (probably per minute) and for mediating 3rd party solutions such as Rebtel (surcharge per minute). Some services that are mostly IVR interface could probably be cheaper than human assisted ones.
None of these services require phone agents to be present in the target country, only the sales agents and DID phone numbers. SIP trunks allow for that.
Even sales agents could be minimised with booking the phone over the Internet, etc. Depending on the cost of the phones, they could be prepaid service or Credit Card deposit type.

This idea is released under Creative Commons Attribution 3.0 Unported license.

Love calls over the IP network

arafalov — Tue, 06 Mar 2007 02:26:25 +0000

I usually suck at Velentine’s day presents. This year, however, I may have just killed several birds with one stone and impressed my wife too.

It all started a couple of months ago, when I noticed ever more frequent mentions of internet telephony becoming a very big thing. I have dutifully subscribe to a couple of blogs, had a quick read of leading websites and left it to stew in the background. The whole VOIP/VoiceXML/CallXML/IVR field looked like a fairly complex field with a steep learning curve.

And so it was until, on the 12th of February I had seen a Telephony Mashup Contest announcement with reasonable prizes, but only 2 weeks deadline. As part of the description somewhere, it was mentioned that free developer accounts were sufficient to get a mashup working.

Suddenly, the whole telephony did not look scary. With timelines so short, it could not be so difficult to get into it and free developer accounts turned out to be rather better than anything I could have imagined. Specifically, Voxeo’s hosted solution provided free access to all I needed to put together an application, including a real-time debugger/tracer. They even gave phone numbers to test the application.

I did not care about building a mashup, but using my technical skills to surprise my wife was another matter entirely.

So, I set out to build a Let me count how many ways I love you application with the code name Valentine. The basic idea is that I leave my wife a phone number to call, but the message at the other end of the phone line is with my voice counting the ways I love her. The interactive twist was her being able to choose the number of ways with DTFM (press 5 for 5 top reasons).

Since Voxeo’s developer accounts are self-provisioned, I was able to get one immediately. They have a good amount of documentation to start, and it took barely 20 minutes to implement and – more importantly – understand their Hello World application. I was hooked.

Voxeo provides both text-to-speech(TTS) and voice recognition as part of free services. I did not need voice recognition, but TTS came very useful during development phase. I used TTS as stubs for the messages until I had the flows ironed out and then replaced all the prompts with my own voice. All in all, it took a couple of hours, with voice recording and uploading probably taking more than the programming itself.

For those who are interested, an early version is available for download. It is in CallXML 2.0, which is Voxeo’s proprietary solution. I used it because that’s what Hello World was in and I did not even notice that CallXML 3.0 and/or VoiceXML was an option. If I had to do it again, I would use VoiceXML/CCXML or at least CallXML 3.0.

Since the Valentine day, I had been looking for other solutions like Voxeo’s. There is free hosting from Tellme, but it requires your own hosting setup and applications need human approval, so the service takes just that much longer to get into.
Either way, I am getting quite excited about telephony, so will see what other interesting things are possible around it.

Where is D.A.V.E – uses for portable wireless storage devices

arafalov — Tue, 30 Jan 2007 16:13:45 +0000

What could one do with a portable hard-drive that can be connected to wirelessly? And with software API to boot. More than one can think!

Robert Scoble has a video interview with a Seagate exec about D.A.V.E/DAVE, the new device they are releasing in the coming months. It is envisaged to be an external storage device for person’s other gadgets with limited memory, such as mobile phones, mp3 players, etc.

They do mention however that there is a device-to-device replication mode. This I think is where it will get interesting for other purposes.

Specifically, I am thinking of public demonstrations and democracy aspects. There had been a long tradition of taking pictures of police response when that response overstep the line and limits. Unfortunately, the same policemen who cross the line of legality like to confiscate and erase the tapes as well.

This is slowly becoming harder to do with proliferation of the camera-phones, but DAVE can change the situation much faster and with more impact for situations known to be dangerous in advance.
All one needs is a digital camera with a wireless transmitter. That is partnered with another – less noticeable – person’s DAVE and the pictures get offloaded in real-time. If the journalist is stopped, the person with the DAVE device may still be able to escape and deliver the photographs/video in time.
Alternatively, it might be possible to setup multiple DAVEs as retransmittion way-points with the content duplicated among many people, with some very far from the demonstration. That way even a live feed might be possible.
The society is becoming more and more transparent in many ways that cause concern. It is good to see that at least some of these technologies can also help keeping the real democracy alive.