Thanks
655 karma · joined January 5, 2013
Envision a world where a google glass like device take see what you are seeing, identify what it you are looking at, figure out if it is an IoT device, notify you in AR if it is (via icon hovering over device or something), allow you to "activate" the device's personified self and talk to it, question it, assign a task to it or a variety of other interactions supported by the IoT device.
Another reason might be the product/technology that the startup is working with that might be of interest to a good employee. Money is not everything.
What Kik seems to have is essentially a web browser with a chat interface overlay where instead of typing in a URL you "mention" (summon?) a bot and the bot then gives you a "button" (link?) you can tap to open the web content.
One thing they do get right though is the idea that the bot should disappear once done and not bother you, however keeping marketers from not abusing that is going to require them to restrict that via code (e.g. session timeout)
Ideally I would want a single conversational chat bot that I can summon, ask to perform a task (regardless of what service is chosen to perform the task), select from the options provided, have the task performed. The bot can select an app to perform the task (deep link) or if no app can do it then some bot (if a bot exists to do that task) or a web link.
HTML5 also has Notifications API[1] which can be leveraged for push notifications on mobile devices.
I do not disagree that there are many use cases for using Apps especially in the Enterprise space but there are far too many consumer apps than enterprise ones so maybe I should change that statement to "a majority of native consumer apps" :)
[1]https://mobiforge.com/design-development/web-push-notificati...
1. Fix app discovery
2. Fix app search before putting search ads. e.g. if your app name has a symbol in it searching by app name will NOT return your app in the search results.
3. App review times can be further reduced by automating the review process
4. Try it before you buy it option
5. Better UX
1. Considering that some of the apartment dwellers will become homeowners and their place will be taken by new apartment dwellers, how will the overcrowded schools support the influx?
2. Considering people will take public transit to go to work, they still would use cars to move around locally in the area on evenings and weekends. How will the current streets support the greater density of cars? e.g. Central Expressway used to be an expressway now it is a parking lot.
3. Overburdened police and firemen will be exposed to further strain.
4. Parking is a nightmare not just on residential streets but even at local establishments. Space needed for parking is used to build more housing.
Unless you live here and face these issues it's easy to downvote rather than come up with solutions that are at pace with the housing construction boom.
If I paid over a million dollars to buy a house in a school district that has a good score what would you suggest I do when suddenly the student to teacher ratio is so skewed that the education of my children suffers?
There seem to be 2 major friction points that prevent one application to be used by another or being a part of a flow:
1) Generating an API
2) Consuming an API
If there was a way to automate API generation based on parameters then presumably a person could create an API endpoint that gets them the data they want and then use that in an IFTTT recipe.
However to use it in an IFTTT recipe the API should also have a specification generated to we can automate a program like IFTTT to look at the specification and create the API consuming code.
So from a simplistic viewpoint it would be better to think of how to create a standardized way to auto generate APIs.
Either way a public outrage was not required unless the owner wanted to ensure he got a new car even if it was the driver's fault. By claiming ""I don't' know if they're going to acknowledge if it was their fault," Puzant said.", the owner wanted to cast doubt on Tesla's integrity and also give himself an "out" if Tesla determined it was driver's fault.
1. Mark Zuckerberg is the Messiah, albeit with human traits of failure. (Makes a messiah more relatable)
2. Google pooh poohs Facebook
3. Google sits up and takes notice as Facebook's users pick up and Vic Gundotra's kids and their friends tell Vic that Facebook is where they are at and Vic goes to Larry Page and whispers warnings in his ears.
4. Larry bestows knighthood on Vic to wage war on Facebook.
5. Vic looks at the Google Landscape and thinks "I bet I can get 400 million users by bombarding Google properties with G+ buttons but that would be too easy so I am going to only allow people with invites to become users. Come on I need a challenge!!"
6. Zuckerberg looks at G+ and Google's search users and thinks "Holy God in Heaven! My flock is under attack"
7. Zuckerberg ushers his flock into the pen and closes the gates.
8. The flock sits in the pen and does what they had been doing though a little more carefully now.
9. Vic looks at the barren landscape of G+ and thinks "There's no one here. I better put cardboard cutouts of people here so Larry doesn't revoke my knighthood"
10. Mark's flock looks at the cutouts and laughs their asses off. They drink some more Kool Aid.
11. G+ is burned to the ground by all the bombardment Vic did and Vic tucks tail and leaves.
12. Mark opens the gates of the pen and his flock are let out and they rejoice. The author of this article thinks Mark is a genius for herding all his flock into the pen and hunkering down.
13. "That's how you "lead" wars, bitch", proclaims the Messiah.
sarcasm