As with most hackers here, a job, a family and an attempt not to burn out has left me with plenty of ideas but with very little to show.
The most audacious one rolling around in my head right now is Notifyway.com. The basic concept is allowing the end user to control how and when they receive communication from a sender (could be an app, your washing machine or Facebook).
The process would be as follows:
1. The customer (lets call him Bob) signs up with Notifyway.com and downloads any apps they want to use (iOs, Android, Windows, Growl plugin, whatever).
2. Bob registers each app as a "receiver" with Notifyway.com using OAuth. This allows push notifications to be sent to each "receiver"
3. Bob signs up with AwesomeService.com which lets him know when there are friends nearby.
4. AwesomeService.com connects to Notifyway.com and Bob authenticates the connection using OAuth.
5. AwesomeService.com finds a friend nearby and connects to the Notifyway.com API with a short and long message for Bob.
6. Bob has decided that AwesomeService.com should send him a text message for each notification if it comes through on weekend. However, during the week, Bob would like all notifications to be sent to Growl on his Mac (if it is during work hours) as he is at his desk all day long. After hours, a Tweet can be sent or a notification on his iPhone. If it is a long message, it should be sent to Bob's personal email as it is likely a marketing message or some other time insensitive update.
7. Bob is able to make decisions on how to receive his notifications using plugins that provide outgoing services (like ifttt)
7. AwesomeService.com have integrated into a single service with a single API for all their communications with Bob, safe in the knowledge that he will get the notification as he wants to get them.
8. Bob is able to disconnect AwesomeService.com if he ever feels they are not providing any value and he is guaranteed no more communication (Bob never even gave his email to AwesomeService.com because it wasn't necessary).
The concept lives and dies on very high volume and would need to have fairly low margins to entice services to pay to communicate with their customers. This would probably need to be driven by customers who would demand integration.
There are services that do something similar things (e.g. Boxcar, Pushover & Notifo) but I don't think they are aligned in the same way. I am hoping to make this an "open service" so the protocol is open, 3rd party apps would be welcome and community contribution acknowledged.
If anyone is interested, I'm starting a design document to discuss the possibilities and opportunities that this service might create.
The most audacious one rolling around in my head right now is Notifyway.com. The basic concept is allowing the end user to control how and when they receive communication from a sender (could be an app, your washing machine or Facebook).
The process would be as follows: 1. The customer (lets call him Bob) signs up with Notifyway.com and downloads any apps they want to use (iOs, Android, Windows, Growl plugin, whatever). 2. Bob registers each app as a "receiver" with Notifyway.com using OAuth. This allows push notifications to be sent to each "receiver" 3. Bob signs up with AwesomeService.com which lets him know when there are friends nearby. 4. AwesomeService.com connects to Notifyway.com and Bob authenticates the connection using OAuth. 5. AwesomeService.com finds a friend nearby and connects to the Notifyway.com API with a short and long message for Bob. 6. Bob has decided that AwesomeService.com should send him a text message for each notification if it comes through on weekend. However, during the week, Bob would like all notifications to be sent to Growl on his Mac (if it is during work hours) as he is at his desk all day long. After hours, a Tweet can be sent or a notification on his iPhone. If it is a long message, it should be sent to Bob's personal email as it is likely a marketing message or some other time insensitive update. 7. Bob is able to make decisions on how to receive his notifications using plugins that provide outgoing services (like ifttt) 7. AwesomeService.com have integrated into a single service with a single API for all their communications with Bob, safe in the knowledge that he will get the notification as he wants to get them. 8. Bob is able to disconnect AwesomeService.com if he ever feels they are not providing any value and he is guaranteed no more communication (Bob never even gave his email to AwesomeService.com because it wasn't necessary).
The concept lives and dies on very high volume and would need to have fairly low margins to entice services to pay to communicate with their customers. This would probably need to be driven by customers who would demand integration.
There are services that do something similar things (e.g. Boxcar, Pushover & Notifo) but I don't think they are aligned in the same way. I am hoping to make this an "open service" so the protocol is open, 3rd party apps would be welcome and community contribution acknowledged.
If anyone is interested, I'm starting a design document to discuss the possibilities and opportunities that this service might create.