Yep, I did indeed say that ColdFusion already supports HTML6 :-)
Over on the Adobe MAX blog, Kevin Lynch just announced that MAX Moves to Spring. The next MAX will be hosted on May 4-8, 2013, in Los Angeles, CA.
Supporting our community has long been an utterly critical part of what I and my team do. My own involvement with the community goes back to the mid-90s (before I joined Allaire), and between MAX and usergroups and community events and more, I personally remain very connected to the community. Indeed, having a dedicated team to focus on, and support, our most loyal and passionate users is a source of much pride for me. But, it's no secret that for the past few years we've not been staffed to provide appropriate local support for communities in Europe (and indeed, all of EMEA). And so I'm really pleased that Christie Fidura has joined our community team as our new UK based EMEA Community Manager. Christie has been with Adobe since 2009, and her prior role did afford her the opportunity for some community involvement, but now community is her full-time job. She has posted a hello message on the community blog, feel free to go by to say hi and welcome her to her new role.
Adobe Creative Cloud, first introduced by Kevin Lynch during the MAX 2011 opening keynote, is now live, and waiting for you to subscribe.
Edge Preview 6 is now available for download, along with a new site at edge.adobe.com. New features in Preview 6 include built-in tutorials, a new code panel, additional language support, and more.
The Flash Professional Glossary page on ADC provides definitions of basic terms and common tasks you'll encounter as you work with Flash Professional. Each entry includes a definition along with step-by-step instructions (when relevant) for completing the task.
We're looking for WebKit engineers, web standards engineers, quality engineers, JavaScript engineers, and engineering managers.
I'm an Android fan. Over the years I've used lots of smartphones running lots of OSs, and Android just works for me.
And yes, I used an iPhone for 5 months before abandoning it. Why? The primary reason was the keyboard. I use my phone for email more than I do texting or talking, and so, for me, the keyboard is critical. Everyone said give it a few months and you'll get used to it, but nope, in all that time I was never able to write a single email or text message without having to go back and make corrections. Plus, iPhone always felt like I was using someone else's device, not one that I could tweak and adjust and tinker until it looked and felt like mine. So, sorry, no iPhone for me. (It's worth noting that when it comes to tablets, I have 5 of them, iPad is my favorite. I use my phone for email far more than I do the tablet, so the iPad keyboard does not stress me out as much as the iPhone one does).
What about Windows phones? The new Nokia Lumia devices running Windows are spectacular, boasting what appears to be the very best email client and support on any device out there right now. And I actually could see myself using one in the future. Perhaps.
For now though, it's Android for me, and has been for several years. I like the OS, I like the options, I like the openness, and I like the flexibility to make the phone my own.
But unlike iOS where you have a single device vendor offering a single experience, Android consumers have lots of options to choose from, and the differences between them range from subtle to significant. Over, the past few years I have tried and used lots of Android phones, and I do mean lots. And here is what I have learned:
Part of what gives Android its flexibility is the fact that device vendors can tweak and enhance the OS to create a unique customer experience. (Of course, this is also what makes Android devices far less consistent than iOS devices). Device vendors do this by creating custom overlays (skins) that sit on top of the Android OS itself. You can indeed buy devices running pure unadulterated Android (for example, the Galaxy Nexus) but most Android devices come with vendor created skins which create the vendor specific Android experience. Ok, keep that in mind, we'll come back to it in a moment.
Motorola brought us the Atrix (and its successor, the Atrix 2), the Droid devices, and more. I've made the switch to Motorola Android devices twice, and gave up both times. For starters, I found the Atrix case to be too plasticy and flimsy, it felt too light and crushable. But the bigger issue for me was the Motorola Android skin, Moto Blur, which at times feels just too heavy and intrusive and in-your-face. Requiring the creation of a Moto Blur account just to turn the phone on and use it? Unacceptable. Custom versions of stock Android apps? Great idea, but not when they feel slower and more sluggish. I've heard that Motorola has recently made changes to Moto Blur so address some of these issues, but I have yet to try the changes for myself. Bottom line, based on my Motorola experiences I'd be hard pressed to try one again anytime soon.
Next up is Samsung, currently the number one Android device maker in the world. At various times I have owned and used 4 different Samsung devices (and several immediate family members have these, too), and the experience makes it easy to understand why these are so popular. Earlier devices, like the Captivate (local version of the Galaxy S) had a really poorly designed case that could open too easily, but those issues have long been addressed. The Galaxy S2 (both the 3G version and the considerably larger LTE version) are well built, feel good to hold, are fast and responsive, and boast gorgeous screens. TouchWiz is Samsung's Android skin, and in addition to being bright and colorful and even fun, it adds useful social integration features, and also replaces or enhances stock apps. But I also find it irritatingly juvenile. From the colored text messaging bubbles to the overly cartoony app icons, at times TouchWiz feels in the way. But my biggest problem with the Samsung devices (and I experienced this on all of them) was a reliability issue with the mail clients. As I noted previously, e-mail is a huge part of what I use my phone for, and I need Gmail and Exchange clients that are capable and powerful and responsive. And while I appreciated the extra features that Samsung added to the stock Android mail clients, problems like mail getting stuck in the Outbox folder forever made them close to unusable. Still, I stuck with Samsung for a long time, and could see myself using one again in the future.
Which brings me to HTC. I was first introduced to the HTC Desire HD by my colleague Serge Jespers who was thoroughly enjoying trying to make me jealous of the screen and performance. He succeeded. I bought the local version of the Desire HD in early 2011, and was hooked. The phone was heavy, but featured a rubberized back, and an industrial design inspired curved case that just felt so good to hold. It also featured one of the worst battery and SIM compartments I have ever seen, impossible to open and harder to close - you can't have it all. HTC has their own Android skin called Sense. It feels lighter weight than Moto Blur or TouchWiz, it's definitely cleaner and more professional looking, and best of all, the enhanced versions of the stock apps feel right and intuitive and even native. Oh, and I have yet to find a single undelivered piece of email in an outbox folder on any HTC device to date. The downside? The AT&T version of the Desire HD was needlessly crippled by really poor radio inclusion which cause no 3G in Europe and no coverage at all in Japan. So a while back I updated to the HTC Vivid, an LTE phone with every radio you could want (it works everywhere), and a stunning screen. It also features a pretty but terribly designed back cover that slides off at the most inopportune times.
You see the problem? I like stock Android, but HTC Sense really does work for me. I want a phone that feels good to hold, and has a solid well thought out case. And I also want every possible radio, a top notch screen, and killer performance. Yep, I want it all.
HTC phones are currently my Android devices of choice. They are not perfect, but they are the best for the type of use (and abuse) I throw their way.
As for what is next? The HTC One X is now days away. Could it be the perfect phone? Stay tuned ...
Andy Trice has created app-UI, a collection of reusable application container user interface components that may be helpful to web and mobile developers for creating interactive applications using HTML and JavaScript, especially those targeting mobile devices. As per Andy, app-UI was born out of the necessity to have rich and native-feeling interfaces in HTML/JS experiences. It works great with PhoneGap applications, and can easily be styled/customized using CSS.
Ray Camden has posted an excellent article explaining the fundamentals of data synchronization between a PhoneGap client and a back-end server.
Join Mike Chambers, Lee Brimelow, Paul Trani, and Renaun Erickson (different presenters at each location) as they chat about the future of Flash, gaming, and more. Upcoming locations include:
- Denver, CO - Tuesday, April 3
- Las Vegas, NV - Wednesday, April 4
- Tempe, AZ - Thursday, April 5
- Nashville, TN - Monday, April 9
- Atlanta, GA - Tuesday, April 10
- St. Paul, MN - Wednesday, April 11
- New York, NY - Thursday, April 12
- San Francisco, CA - Tuesday, April 16
- Los Angeles, CA - Date TBD
- Chicago, IL – Date TBD
Title says it all, 