- Apple Patent on Learning-based Estimation of Hand and Finger Pose — machine learning to identify gestures (hand poses) that works even when partially occluded. See writeup in Apple Insider.
- The Internet of Kafkaesque Things (ACLU) — As computers are deployed in more regulatory roles, and therefore make more judgments about us, we may be afflicted with many more of the rigid, unjust rulings for which bureaucracies are so notorious.
- Schmidt and Hunter (1998): Validity and Utility of Selection Methods in Personnel (PDF) — On the basis of meta-analytic findings, this article examines and summarizes what 85 years of research in personnel psychology has revealed about the validity of measures of 19 different selection methods that can be used in making decisions about hiring, training, and developmental assignments. (via Wired)
- Complete Force Control in Constrained Under-actuated Mechanical Systems (Robohub) — Nori focuses on finding ways to advance the dynamic system of a robot – the forces that interact and make the system move. Key to developing dynamic movements in a robot is control, accompanied by the way the robot interacts with the environment. Nori talks us through the latest developments, designs, and formulas for floating-base/constrained mechanical systems, whole-body motion control of humanoid systems, whole-body dynamics computation on the iCub humanoid, and finishes with a video on recent implementations of whole-body motion control on the iCub. Video and download of presentation.
Truly disruptive services don’t just digitize the familiar. They do away with it.
The Apple-Pay web page gushes: “Gone are the days of searching for your wallet. The wasted moments finding the right card. The swiping and waiting. Now payments happen with a single touch.”
What’s wrong with this picture?
It’s describing the digital facsimile of a process that is already on its way to becoming obsolete. But truly disruptive new services don’t just digitize the familiar. They do away with it.
I never search for my wallet when I take an Uber. I never search for my wallet when I walk out of a restaurant that accepts Cover. I never search for my wallet when I buy something from Amazon. I don’t even search for my wallet when buying a song from iTunes — or, for that matter, an iPhone from an Apple Store.
In each of these cases, my payment information is simply a stored credential that is already associated with my identity. And that identity is increasingly recognized by means other than an explicit payment process. Read more…
Part One: Easily find Chromecast devices on your local network
Now that Google has opened up the Chromecast API for anyone to play with, it’s possibile to create iOS applications that can leverage the $35 device as a way to display to HDMI devices wirelessly. In this series of tutorials, we’ll go over the API, starting with configuring your project to use the framework, and finding devices out on your local network to play with.
Let’s assume you’ve set up a Chromecast device attached to an HDMI TV and have it configured for your local network. Now it’s time to get an App set up to use it. We’ll use the iPhone Simulator in these examples, since it can talk to Chromecast devices just like a physical device, as long as the Mac you are developing on is on the same LAN as the Chromecast dongle.
Begin by creating a project, as usual. For this example, I used a single-view Storyboarded app. I set up an
UITableView inside the default
UIView, hooking it’s datasource and delegate to the default view controller the wizard had created. Next, I went to the Google Google Cast API page and downloaded the iOS framework, then used the “Add Files…” project option to add the framework to the project, copying in the files.
Rosie the Robot may feel more comfortable talking to Siri than to you
Recently, Glenn Martin wrote an article describing how robotics in moving out of the factory and into the house. And while Glenn restricted himself mainly to the type of robots that pop into your head when someone says the word (either the anthropomorphic variety or the industrial flavor), the reality is that there are a lot of robots already in the hands of consumers, although it might take a moment to recognize them as such.
I’m speaking of drones, and especially quadcopters, which are proliferating at an enormous rate, and are being used to do everything from documenting a cool skateboard move to creating a breathtaking overflight of a horrific disaster site.
All predictions are for entertainment purposes only!
It is a generally accepted requirement that all technology pundits attempt a yearly prognostication of the coming 12 months. Having consulted my crystal ball, scryed the entrails of a falcon, and completed a 3 day fasting ritual in a sweat lodge set up inside a Best Buy, I will now tempt the Gods of Hubris and make my guesses for the year in mobile.
Plus ça change, plus c'est la même chose.
As the end of December approaches, it’s time to take a look at the year that was. In a lot of ways, 2013 was a status quo year for mobile, with nothing earthshaking to report, just a steady progression of what already is getting more, um, is-y?
We started the year with Apple on top in the tablet space, Android on top in the handset space, and that’s how we ended the year. Microsoft appears to have abandoned the handset space after a decade of attempts to take market-share, and made their move on the tablet space instead with the Surface. In spite of expensive choreographer board room commercials, the Surface didn’t make a huge dent in Apple’s iPad dominance. But Microsoft did better than Blackberry, whose frantic flailing in the market has come to represent nothing so much as a fish out of water.
Getting apps into the store is a non-deterministic process
One of the major topics of my Enterprise iOS book is how to plan release schedules around Apple’s peril-filled submission process. I don’t think you can count yourself a truly bloodied iOS dev until you’ve gotten your first rejection notice from iTunes Connect, especially under deadline pressure.
Traditionally, the major reasons that applications would bounce is that the developer had been a Bad Person. They had grossly abused the Human Interface standards, or had a flakey app that crashed when the tester fired it up, or used undocumented internal system calls. In most cases, the rejection could have been anticipated if the developer had done his homework. There were occasional apps that got rejected for bizarre reasons, such as perceived adult content, or because of some secret Apple agenda, but they were the rare exception. If you followed the rules, your app would get in the store.