Aldon Hynes's blog
Yesterday, I blogged about my plans to get together with a friend to talk about Glass development. I went on to share some initial thoughts, which mostly revolved around Glass as a device used to retrieve information. Yet much of today's discussion focused on a different aspect of Glass, Glass as a sensor, used to transmit information.
I touch on the Glass as sensor a little bit, at the end of yesterday's blog post, when I talked about using it in fitness, along the lines of Fitbit. Yet my friend, an MIT engineering graduate, and son of a retired MIT professor, with strong ties back to his alma mater encouraged me to think more about Glass as sensor.
In the past, we had worked together on complex event processing projects and developed code for analyzing complex data using Matlab. We talked a lot about various sensor related projects at MIT, so this shift of discussion wasn't a surprise.
What information is Glass capable of gathering right now? Images. Sounds. Location. Can it gather fine motions? Temperature? Other data? What might one be able to do if one could take this information and use it to trigger events?
How can this information be accessed? It looks like location information can be subscribed to with the Mirror API, but other information may need some sort of special Android App for Glass to be developed.
So, I'm starting to explore a little bit more working with the Mirror Api. I've sent messages to my Google Glass from the sample apps as well as from the playground. Next step will be to create something on my server.
Now, I've spoken with a few different people about developing for Glass. It will be interesting to see who comes up with what.
This weekend, I'm getting together with a long time friend and software developer with whom I've worked on many interesting projects. We'll spend some time thinking and talking about what could be done using Google Glass.
I've commented to people that Glass is still a prototype and there isn't a lot out there for it yet. You can send pictures and videos to Google+ Twitter, Facebook, Evernote and probably a few other locations. You can get limited notifications from Twitter, Gmail, CNN and the New York Times. You can search information and get directions. I did find a fitness app being developed which I tested once and should test more when I get a chance.
Currently, I've been using an app called FieldTrip on my Android phone. When I am near a location of interest, a message pops up on the phone about the location. This would be a nice app on Glass, especially if you could select different topics your interested in having pop up. My understanding is that Ingress uses the FieldTrip framework, so getting Glass to send me a pop up message when I'm near an Ingress Portal would be very nice. Adding filters, so it would only pop up if the portal was a certain level or controlled by a certain faction would also be nice. Advanced features might be to look for specific portal owners, mods, etc., sort of like some of the stuff in Ingress Intel Total Conversion.
There is a development platform, which on first glance appears somewhat limited, but has potential. One of the things I'm particularly interested in building frameworks. I've worked a lot in Drupal over the years, so I'm interested in a Drupal module that would allow for the easy access of nodes via Glass. I'm also interested in some sort of Wiki for Glass. At work, we use Microsoft's Sharepoint as well as Microsoft's Analysis Services, Cubes. A framework for accessing Sharepoint or Cubes would also be very nice.
Making it so the Drupal nodes, the Wiki entries or Sharepoint pages could be geotagged and pop up in a FieldTrip like App would be really nice. Ideally, a FieldTrip app, or something related, which could pop up messages from any selected set of sources would be particularly cool. For work, my interest in data in the cube is not particularly geocoded. However, I did some experimenting with PostGIS a while ago and having a Postgres, or other database that could have geocoded data and pop up messages from that data could be very interesting. For example, MySQL with OpenGIS extensions support a distance calculations. For a starting point on this, I looked at New UDF for MySQL 5.1 provides GIS functions distance_sphere() and distance_spheroid()
Imagine census data, population health data, or health disparity data in a geocoded database. When you enter an area where some data point meets a certain criteria, a popup shows up on Glass.
"Woodbridge, CT: Zip 06525, 2010 Population 8,990 41.9% Graduate or Professional Degree, 22.4% Italien"
For that matter, a Fact Finder Google Glass App would be very interesting.
I suspect a lot of this stuff would be fairly easy to develop using the existing Mirror API. As an aside, I should really spend a little time getting up to speed in Go and Google's App Engine.
However, there are lots of other aspects of Glass that I'd love to see developed, which probably go beyond what you can do with the Mirror API. I don't know how much computing power is available on Glass, but I'd be very interested in seeing if Glass could do Eulerian Video Magnification. The health care applications would be fascinating.
I also like to think of Glass in terms of the larger set of technologies I'll refer to as wearable computing. I include things like the Pebble Watch and Fitbit. Imagine the capabilities of Glass, Pebble, and Fitbit combined into one device. You could go for a run, see your course, distance, speed and splits. You could add in information, like for a race course, how far you are to the next water stop, or how your doing against other people using the same device. It could monitor your heartbeat, perhaps even your blood oxygen levels, and give you warnings if you are over exerting yourself, or perhaps encouragement to push harder if you aren't exerting yourself as much as you should.
There's plenty more to think about for Glass Development, but these are a few of my starting interests. What do you think?
Last night, I had a strange dream, the details of which escape me, but two different ideas stuck with me.
First, it was winter time. We were wandering around some town where there were first night activities, not too much unlike Middnight on Main in Middletown. Fiona want s'mores, but we couldn't find any graham crackers or chocolate. By chance, we wandered into a cupcake store and convinced them to make up graham cracker and chocolate cupcakes which we cut in half and put the toasted marshmallows in. It seems like a good opportunity for a cupcake store, find campfires to sell graham cracker and chocolate cupcakes, or perhaps even organize a community event for toasting marshmallows and using their cupcakes.
This led to singing around the campfire. I know why it ended up this way, but the music was printed on flash paper which we threw into the fire at the end of the song adding special effects. Perhaps the fireworks from last night added to this image.
In 1996, Richard Bartle wrote and article, Hearts, Clubs, Diamonds, Spades: Players Who Suit MUDs in which he explored four basic player types in text based virtual reality games called MUDs or Multi-User Dungeons. He summarizes these types as follows:
So, labelling the four player types abstracted, we get: achievers, explorers, socialisers and killers. An easy way to remember these is to consider suits in a conventional pack of cards: achievers are Diamonds (they're always seeking treasure); explorers are Spades (they dig around for information); socialisers are Hearts (they empathise with other players); killers are Clubs (they hit people with them).
He uses this to explore ideas like game stability and player interactions and recently, I've been wondering how this relates to the Augmented Reality game, Ingress.
In Ingress, players interact with one another, destroying opponents portals, fortifying portals that other faction members have captured, recharging portals, exchanging gear, etc. There is an achievement aspect in terms of what level one is and how much gear one as accumulated.
I suspect that the player styles may change as people level up as well as when an area gets more players of one faction or another, and that each player has a little bit of each style.
For example, I probably started off primarily as an achiever, seeking treasure and trying to level up. Once I reached Level 8 in Ingress, which is currently the highest level possible, my focus on seeking treasure has diminished, but I still seek a basic amount of treasure. Now that I'm Level 8, I tend to move more towards being an explorer or a socializer. I like exploring new areas and I like interacting with players.
I've met some players who fit very nicely in the into the socializer category, always dropping inventory for new players and helping them get started. I've ran into players who remain very focusing on achievement, trying to build up Level 8 farms, and gather as much gear as they can from them. I've run into others that focus mostly on tearing down other people's farms.
Another component of Ingress is establishing links and fields. With this there are several different styles, that I haven't really figured out how they best fit to Bartle's model. Some people rarely link, or create links to support a farm. Others create long wild links, which make it difficult for others to link but don't serve any other apparent purposes. These links are used to establish fields. Some people establish large fields, mostly as an achievement, which the killers take down as soon as possible. Others create lots of small fields, overlapping as much as possible.
Bartle spends a bit of time talking about interactions between different styles of players and it is useful to read through the section, think about what sort of player you are, what sort of players are around you in your faction, and what sort of players are in the opposing faction. It may provide insights that can make the game more fun for players, no matter what style they adopt.
So, do you play Ingress? What style of player are you? What style of players are around you in your faction? What style of players dominate the opposing faction? How do these insights change the way you approach the game? Or, do you think Bartle's ideas don't translate to Ingress? Is there something that better explains player interactions? Let me know your thoughts.
Rabbit, Rabbit, Rabbit. The persistent light summer rain has yielded to the occasional residual drops falling from leaves and gutters. July has arrived and I greet it with the monthly harkening back to simpler days of childhood where three small words could invoke good fortune.
May was the busiest month, and I had hoped that things would slow down in June, yet it was still so busy that I needed to carefully plan out each day. I haven't written a similar plan for July.
I took Friday off from work, and even though it was a busy day, going from a funeral to a swearing in ceremony, it still felt like a day off. Saturday was full of the typical summer time tasks, a trip to the dump, mowing the lawn, swimming at the pool, and then gathering with some long lost friends of Kim, it also had summer pacing to it.
Some of this is due to a nasty canker sore that has been afflicting me. I am assuming it is this canker that has resonated through out the right side of my head causing an earache, headache, and fatigue. I slept as much as I could during the weekend and am still tired.
I won't end this blog post like I do many other start of month blog posts, highlighting the upcoming planned activities. Instead, as much as possible, I'm planning on slowing down and listening to the last drops of a summer rain storm fade into the sound of birds greeting the morn.