So, as you know, iOS 8 finally brought IndexedDB to Mobile Safari. I may be biased, but I find features like this far more useful than CSS updates. Not to say that I don't appreciate them, but to me, deep data storage on the client is something that is more practical and useful to more people. Of course, I work for a company that is all about designers and not developers, so what do I know? ;)
Pardon the cryptic title. Earlier this morning I was working on a demo (the result of which is documented here) that I knew was going to be rather simple. Therefore I decided to skip using Ionic since AngularJS would have been overkill for what I was producing. I was ok with that, but what I really didn't like was losing live reload and logging in my terminal. Turns out there is a rather obvious way to get that.
iOS8 launched yesterday and it has damn good updates in mobile Safari. I strongly suggest folks read Max Firtman's detailed review here: iOS 8 and iPhone 6 for web developers and designers: next evolution for Safari and native webapps. One thing missing, however, is support for datalist controls. I've blogged about them before and I really like how simple they make basic autocomplete controls. I noticed over on the CanIuse page for datalist that Android 4.4.3 and higher now support it. Here are some screen shots of it in action. Honestly it looks pretty much as you might expect, but I wanted to see for myself.
How cool is NCDevCon? The presentation I finished 10 minutes ago is online. Now. There may be some audio issues in the middle (had some feedback) so you may want to switch to headphones (let me know), but overall, check it out and let me know. I've made no secret of my love for Ionic and I hope this helps people get acquainted with it.
p.s. I didn't include my slide deck and example apps, but if folks would like them let me know and I'll post a copy.
Most online forms don't allow HTML, or allow a very strict subset of HTML, but for years now my blog form (the one I'm using right now) has allowed for any and all HTML. I figure if I can't trust myself, who can I trust? Of course, from time to time I screw up and forget to close a tag or make some other mistake. For a while now I've wondered - is there an easy way to check for that and potentially catch those mistakes before I save the form?
Yesterday the Ionic folks released version 1.2.0. They've got a nice blog entry taking about the update, but I want to share the cool bits here as well. Definitely read their blog post for all the updates, but here are the ones that I think are really cool.
Earlier this morning I saw the following tweet:
I've been meaning to write this up for a while now, but I never got around to it till today when a meeting got cancelled suddenly. It was this or get on the treadmill, and unfortunately, the treadmill lost. Lately I've noticed a common problem with both web apps and native apps. The problem is this: The application renders some sort of dynamic content. In that content are various UI elements you can click. At the same time, the app is fetching additional content asynchronously. When that content comes in, it is displayed then and the layout of the content is adjusted as the new stuff comes in. The problem is that the user may have been just about to click on a button, link, or whatever, and now finds that their click action has done nothing. Or worse - has activated another action that they didn't want. TweetDeck is especially bad about this. Facebook, surprisingly, is actually pretty darn good about this. Let's look at a simple example in case I'm not making sense.
For a while now I've been praising the the Ionic framework as one of the coolest things to happen to Cordova/PhoneGap development. I kept promising to talk about it a bit more deeply on the blog and today I've finally gotten around to it. This will be somewhat long, and rambling, but I hope it will give readers an idea of why Ionic is so cool and why they should consider giving it a try.