I had such a great time working on this, I can't even begin to tell you how much I enjoyed this project. Apple Watch? Check. Anticipatory Mobile App? Check. Coffee? Double check! One of the things that I believe is (or should be) on everyone's bucket list is a chance to create something that's never been done before. This was my opportunity to check that off mine. Richly rewarding, amazingly collaborative... and let's be honest. Cool as hell.
This week, ahead of schedule and under budget, my team delivered a hugely successful mobile deployment for the United States Marine Corps. A terrific example of powerful teamwork and collaboration, this project represents a continuation of the increasingly complex work we're doing in mobile. With a mobile display layer that accommodates a huge array of handsets and screens, this one was a nice sized effort that required tremendous oversight and a lot of planning & strategy. One of the biggest challenges with this project was leveraging the existing CMS for content, while presenting larger, longer-form experiences in smaller, bite-sized chunks. We needed to build over an existing infrastructure, a way to take content that was originally (and optimally) designed for a desktop experience, reduce it in both size and scope, and wrap it in a mobile display layer that still reflected both the brand and a look & feel consistent with the desktop experience. Mission accomplished. Check out some of the shots below, and make sure you take a look at the website in your mobile device.
How do you demonstrate the value of switching to Pennzoil? How do you take a bunch of car data, mash it up with fuel efficiency formulas and communicate (effectively and in an engaging way!) why you should switch to Pennzoil? How do you show, in a tangible way, what those savings represent? This week, my team launched a Pennzoil Fuel Calculator on Pennzoil.com. I was once again completely blown away by the work my Creative Technology group did on such a fantastic jQuery parallax calculator experience. The Pennzoil Creative team knocked it out of the park with their design work and guidance, and we were able to pick up on their vision and make it a reality. I personally enjoyed watching what happens when you sit creative down at the desk next to developers and get out of the way. Remember, the cleanest lines of communication are the shortest. Put the guy (or gal!) building it next to the guy (or gal!) whose idea it is to build it, and you get sweet, sweet results.
When you're responsible for technology, sometimes it can become all too... tactical. You begin to quickly get to "the solution" place and by the time you're reading this, we've already arrived at the end and are just waiting for you to get here. It's an engineering trap. Forgetting you're creative. Forgetting that you have a spark, or a natural curiosity; a desire to create things, build stuff. Sometimes you simply forget to come up for air and look around and smell the proverbial flowers. So one of the first things I did when I took over Creative Technology, Database, and Analytics for JWT was work very hard to focus on the idea, "sure, you're a developer, I get it... you're an engineer, but you build stuff... you're inherently creative and you work in a creative environment... embrace that shit". I wanted my gang to enjoy using the right side of their brains. So I offered them up a little somethin' somethin' to get their creative juices flowing: I would buy anyone who wanted to sign up a Raspberry Pi and Arduino and let them do anything they wanted. Client related, not client related, fun, experimental, new... whatever they wanted. The only catch was, you had to come back in 90 days and give a presentation on your project. You had to tell us what your big idea was, what inspired you, and how you did it... oh, and you had to demo your project. Five teams signed up. I was impressed right off the bat that it wasn't individuals that signed up, but that my offer spawned several conversations among like-minded, organic groups (who, I might add, didn't normally work together... so there's that!) that evolved into formal ideas. There was a demonstration of Raspberry Pi running Xbox Media Center (XBMC), the open source Home Theater Software. A terrific idea involving geo-fencing/mapping, and outdoor location. One of my lead developers put together a demo/presentation of a larger idea for a "Holiday Card" that could potentially bridge the gap between two remote locations in a fun, engaging, and ultimately very impressive manner (that one I kept in my back pocket. As soon as I saw the idea I just told everyone in the room, "okay, we're building THAT one this Christmas... you watch"). An iPhone powered paintball gun that was one of the highlights of the demonstration and created such an active discussion in the room, that it went from "An iPhone Powered Paintball Gun" to a "Twitter Powered T-Shirt Cannon" in less than five minutes. Finally, one of the engineers on my team who's perhaps the quietest person I've ever met (he literally sits all the way in the back corner of the office) decided to take my offer of gratis computer power, marry it with a couple of hundred dollars worth of hardware and create a Microsoft Kinect powered, wi-fi enabled, remote controlled car. The beauty of this idea was that you didn't even need to be in the same room as the car. The car contained all the computational power and network capability, and using node.js, was able to maintain a connection to a remote server that was coordinating the motion and movement. Theoretically, you could control a remote-controlled car on the other side of the world using just your body. Crazy shit, right? I relish my technology leadership role, but too often it can become mired in the tactical. The "throw it over the fence and build it" that sort of naturally occurs in these environments with their deadlines and requirements. It's not bad. It's the job. It's just that sometimes it's nice to stop and smell the roses.
I just got back from "An Event Apart" in Atlanta. This is the second AEA that I've attended, the first being in New Orleans several years ago. If you've never attended An Event Apart, it's a truly inspirational conference. Creatively merging design, development, and mixing them all in a tall glass of web standards, it's really the one other conference, besides Adobe Max, that I feel is a legitimate, "must-attend" learning experience. It's not for the feint of heart however, it's a lot of information over a small amount of time. You're exposed to an eclectic mix of speakers and topics ranging from high level design discussions to low level, technically challenging sessions like the nuts and bolts of CSS, or technical executions of cutting edge HTML5 solutions. It's not like MAX, where you're moving from venue to venue over the course of a couple of days, interspersed with keynotes and scoping the sponsor pavilions. You're essentially in the same place for two straight days (three if, like us, you attended the additional "A Day Apart" session on devoted solely to "Content Strategy"). Spending two days in the same room can sometimes try even the most patient observer, but the topics breeze by and the challenge instead becomes, "how do I make sure I'm taking this all in?". Luckily, the brilliant guys and gals at AEA make the presentation slides available to attendees, and armed with an iPad, I quickly discovered the best way to keep up. Each day, before that day's sessions, I would download all the presentations to my iPad and set it up at my spot, allowing me to keep up with the talking points on a provided pad of paper. Yep, good ol' pen and paper worked better than anything I could come up with, and leaving my laptop up in the hotel room enabled me to really concentrate on what was being presented. In fact, this worked so well I think I'm just gonna plan on attending future conferences armed with a moleskine and a pencil.
Last year at Max, there was ONE demo that rocked my world. In fact, it rocked my world so hard, I went on a mission to find Doug Winnie and pick his brain. I was singularly focused wandering the expo hall like a zombie asking everyone wearing a black shirt, "hey, have you seen Doug Winnie?" It was code named, "Edge". It's described as, "an HTML5 animation and interactive design tool". Did you read what I just wrote? Stop for a minute. Go back and slowly let that sink in. The company that owns Photoshop, Flash, Dreamweaver, inDesign, After Effects, Flex, ColdFusion and a whole host of other visual design tools is developing a product that allows you to create interactivity and animation with web standards technologies like HTML5 and CSS3. When I saw the demo in LA last year, I practically shit myself. I literally can't wait for this product, and I want you to know, I didn't use the word "literally" where I should've used the word, "figuratively". No, I literally can't wait for this product. Watch Doug give you a couple of brief overviews:
I only briefly blogged about Dreamweaver CS5.5 the other day and embedded what I thought was a great video of Greg Rewis going through all the bells and whistles of the latest release. He's got a great blog post on the subject, so I felt like the topic was being covered pretty well. But I realized, dammit, I love this product so much that I'm gonna go ahead and toss my two cents out there regardless. I think over the next month or so I'm going to try and blog as much as I can about little features, tips, tricks, and particular things that I love about the app that maybe people who are new, or perhaps haven't dug into it might not be aware of or maybe haven't had an opportunity to use. The first thing that I want to point out is what I call, a "one-two punch in the face". This is the combination that just knocks me out. I don't even really need to start a discussion by saying things like, "hey, have you heard? Mobile is big now..." or, "have you seen these 'smart phones' that all the kids have these days?". I think now, all we need to say is, "Mobile is here. Now". For years and years people have been talking about it and I sat in on sessions at Max in the early part of the "aughts" that predicted this as, "just around the corner" but I don't think any amount of hyperbole could be used today to describe the impact of mobile on workflows. It's for this reason alone that I'm excited enough about Dreamweaver CS5.5 to make sure I got my pre-order in the day it was available. With this release of Dreamweaver, Adobe has added two features that, I know at least for me, are game-changing. jQuery Mobile support, and PhoneGap. Let me be clear, too. It's not just "support" for the PhoneGap framework. It's the PhoneGap framework built right into Dreamweaver. We're talking package your app for app stores and launch the emulators right from within Dreamweaver. Web developers can now call native APIs like notifications, camera, contacts, etc from PhoneGap now within Dreamweaver CS5.5! My friend, Scott Fegette over at Adobe has written an excellent overview piece on how this integration looks in the upcoming release. Check out this money quote:
For Android, the complex process of installing, configuring, and verifying the Android SDK has always been a bit of a chore. Dreamweaver CS5.5 takes all the pain out of this process by providing an "easy install" option, which will do all of the above for you in the background. Although the Apple iOS SDK tools are subject to a different licensing model (and only available on the Mac platform), once you've installed the Apple iOS SDK (or Xcode from the Mac App Store), you simply point Dreamweaver CS5.5 to the /Developer directory on your hard drive and you're ready to go.Now, I'm not even about to go down a road about how this "replaces app development", or "now you don't have to learn Objective C or Java for Android". Nope. That's not the case at all. I think those skills are still going to be needed, but what I do see is the ability to deliver mobile content to a wider audience of clients and customers without the barrier of a potentially costly endeavor. Look, I've got clients who don't need a game. They might not need an overcomplicated app requiring a computer science degree. They're clients who have an idea or a product they want to expose to the mobile space where a nicely wrapped HTML/CSS/jQuery mobile experience is perfectly acceptable. Both from a cost standpoint and a deliverable experience standpoint. I think there are plenty of opportunities worth exploring for a wide variety of clients who probably haven't gotten into the app space precisely because of what I'll call, "the app barrier". Now, I think it's safe to say that Adobe and Dreamweaver have significantly lowered that barrier and allowed me to provide tremendous value to clients. For more information about all of this, you simply MUST go check out the Dreamweaver Channel over on Adobe TV.