A new Grails plugin: Invitation-Only
This morning I released a new Grails plugin that lets you manage beta-invites to your app and similar.
This morning I released a new Grails plugin that lets you manage beta-invites to your app and similar.
I sent a wide-ranging complaint letter to The Co-Op after hitting saturation point with the continued problems with their online business banking, a catalogue of mistakes and inefficiencies making international payments, and continuing frustrations with the idiotic personal banking chip reader and antiquated personal banking site.
You know, little things. My complaint was very much supportive of the banks ideals and its original market-leading position on online banking.
Anyway the response has finally come. To paraphrase:
Let’s not hold our breath. New business banking has been in development for years, only just rolling out. Timescales given out for it last year, still not met revised dates.
There have been lots of iPad reviews, so I’ll try not to go over the same old stuff. Suffice to say it is very good, but I’m still learning how to use it – i.e. how it fits into my life. Will I really do diagrams on it, will I read e-books for long periods, will I write code?(?!).
A quick summary after 2 days intermittent use.
I can’t vouch for Pages, Numbers, Keynote or iBooks yet – they aren’t available in the UK app store (which you can only access from iTunes currently anyway).
The Weceem CMS plugin for Grails uses the Blueprint CSS framework, jQuery and jQuery UI Javascript libraries. As the Grails plugin marketplace continues to mature, other plugins will have more polished user interfaces or reusable tags that require certain libraries.
This raises an ugly prospect: a new resource dependency problem. Only unlike java dependency problems this is worse as you end up with multiple copies of resources in your app, even if they are the same version because plugins will typically bundle the resources themselves. Your app may add some of these too and your site becomes slow to load or experiences failures related to clashing library versions.
There is however a staggeringly simple solution to this: lightweight Grails plugins that contain the resources.
Thanks to Grails’ automatic dependency resolution we (the grails community) can just create plugins to wrap up each such library and then we just make any apps or plugins that require them depend on them by installing the library plugin or adding it to the dependsOn clause of other plugins.
An important caveat here is that the library plugins need to use version numbers matching the version of the library they encapsulate. Then if you want jQuery 1.4.2 you depend on/install grails-jquery version 1.4.2 or higher. The grails-jquery plugin authors have already done this.
These plugins should implement a simple tag called “resources” in an appropriate namespace e.g. or .
I strongly believe that such plugins should NOT include other tags or more heavyweight tags wrapping up library features – do that in another plugin e.g. “grails-jquery-tools”.
This approach does provide new challenges for optimizing static content – minifying JS and CSS and including only required modules from a larger library remains awkward as it is today with non-dependency solutions.
Ultimately I think we need smarter solutions than those currently in use to solve this. I have some ideas forming…
I hope to be proven wrong, but I fear that the ongoing Co-operative Bank Business Online Banking fiasco is going to degenerate even further.
The co-op bank have published a short video screencast demoing their new system, presumably to make us believe they might actually come up with something usable any time soon. The new system is already overdue, pushed back to Q2 2010 which we are already into.
Why am I whining again about this? Well if you watch the video pay attention to some of the details.
First – you need a code generator device just to LOG IN. Yes that’s right. You need a CUSTOMER ID, and a USER ID (hey I’m a small business, there’s only me!), and a generated passcode from those crappy machines that need your card and PIN entry. This mechanisms is supposed to make you more secure – but the way Co-op use it on their personal banking is a complete nightmare. You can’t even transfer a few quid to one of your own accounts, pay a bill (already set up) or amend an existing standing order without having to grab a registered debit card AND the code generator device. It makes the entire process extremely slow and awkward. What about people who work on the move? This is not user friendly at all. Using it to log in is a nightmare.
Second – notice how the transaction display in the video is a complete usability cock up. It shows 3-4 lines of balances without scrolling, despite there being much more screen space. It has a horizontal scroll bar all the time, because there are too many columns shown. Even with this, there’s not enough space given to the name of the account and it wraps after only a few characters. All this can be fixed quite easily but the point is it betrays a complete lack of understanding of usability.
On the plus side, I do notice from the navigation menus shown that there appears to be an ability to search for transactions, although you’ll forgive me if I don’t hold out much hope for the actual implementation of this being any good.
There’s however no mention of an international payments option, which presumably – and rather insanely in 2010 – still requires a FAX sent to their offices, on “headed notepaper” to be acceptable. I know, I had to do this last week. It is so antiquated and so foolish. FAX is inherently insecure, and you could easily fax all your bank details to the wrong person if you get the number wrong. Add to that the hilarious false assumption that “headed notepaper” is of any valid use in judging authenticity at all. They don’t know what my headed notepaper looks like. In fact I don’t have any. I sent it with a default template from iWork. And yet if it doesn’t look like “headed notepaper” they won’t accept it.
Laughable. Wake up banks! We don’t user typewriters, telex or fax any more, even if you do in your antiquated businesses.
Recent Comments