Aurelia UX

http://blog.aurelia.io/2016/11/04/introducing-aurelia-ux/

by toddwprice • 10 years ago

90 34 10 years ago

blog.aurelia.io

prplhaz42• 10 years ago

Interesting project...seems like the main competitor here is Ionic? Not sure how to go about identifying and comparing the strengths/weaknesses, but that should come with some time.

Hope this is captured somewhere else, and not just buried in this article...

> Unfortunately, we won't be able to continue our work on AI (Aurelia Interface). After careful consideration and review, we realized that AI was going in the wrong direction and didn't have the versatility or the proper architecture to handle our vision of a UX Framework. With Aurelia UX, we're rebooting our efforts.

oblio• 10 years ago

What's AI in this context? Aurelia I..?

prplhaz42• 10 years ago

Updated post to clarify - Aurelia Interface - their (formerly) commercial UI components.

king_magic2• 10 years ago

Well, if they can somehow make Cordova less awfully terrible from a UX perspective, more power to them. I'm not holding my breath, though.

GordonS2• 10 years ago

Both Ionic and OnsenUI do a pretty good job

king_magic2• 10 years ago

I've seen nothing but awful results from Ionic.

spankalee• 10 years ago

I wonder how Aurelia's style encapsulation is different from Shadow DOM, or how CSS databinding is different from CSS custom variables.

You can already use media queries + CSS custom variables today to do pretty powerful script-free responsive layouts: https://github.com/PolymerElements/app-layout/tree/master/ap...

mattbeckman• 10 years ago

Our team has been using Aurelia for many months. While it has some cool features, there are plenty of gotchas that add a lot of overhead. Weeks spent on features that had to be reworked due to edge cases in DI, for example, or relying on some of the non-core packages.

It's interesting stuff, but don't jump into it expecting to run at full speed without tripping a few times along the way.

fvdessen3• 10 years ago

I have the same experience, We have been using it for months and I cannot say that we are happy. A lot of bugs, a lot of missing documentation, a lot of bloat, and some bad breaking changes. It seems to me that the Aurelia team wants to do too many thing at once, and cannot deliver to the standards that other framework provide.

It's sad because the underlying ideas are good. It is in many ways similar to Vue.js, which is very good. To readers considering Aurelia I would suggest trying Vue as well, or wait until Aurelia is more mature.

pwkad2• 10 years ago

Aurelia is arguably more mature than vue though I guess that depends on who you ask. Can you reference any bugs? Currently most issues that are open on the main repositories are feature requests or edge cases

atan• 10 years ago

To readers considering Aurelia I would suggest trying Vue as well...

And if interested in Vue, check out Quasar [0], a UX framework for Vue (recently made compatible with Vue 2.0) that seems to have a lot of the same goals as Aurelia UX.

[0] http://quasar-framework.org/

ourmandave• 10 years ago

This is a pre-alpha release. So, those adopting it should be prepared to deal with regular breaking changes.

Calling Component Authors

We know we've got a ton of members within our community who have built and want to build components for Aurelia. We're inviting you to join with our core team to build out the components of the Aurelia UX library.

pwkad2• 10 years ago

Can you give some examples on edge cases with DI? Most things that don't work well with DI are due to bad patterns that just need a better resolving strategy which are available or customizable

emilong• 10 years ago

Having never heard of Aurelia before, I was curious how this compared to React and found this interview with the creator/lead, Rob Eisenberg, with his thoughts:

https://medium.com/hashnode-insights/rob-eisenberg-on-aureli...

Also includes his comparison to Angular.

mhd• 10 years ago

Decent grid widget that let's me get rid of ExtJS included?

TheAceOfHearts2• 10 years ago

Depending on what you mean by grid, you might find react-virtualized [0] interesting.

[0] https://bvaughn.github.io/react-virtualized/

jessedhillon• 10 years ago

Major flaw with that component: the scroll handle size does not change. So if you have 10,000 rows, moving the handle down by one pixel will take you from entry #0 to ~#40. In fact, somewhere between 10k and 100k, it stops being possible to scroll to some elements, say from #0 to #20, whether using the wheel or the scrollbar.

nulagrithom• 10 years ago

Documentation:
Forthcoming...

I feel like introducing something without documentation is a little premature. Or maybe its use is abundantly clear to those who've used Aurelia.

kylestlb• 10 years ago

The disclaimer on the site says it's in pre-alpha. I assume that the people trying this out will be people who currently make things with Aurelia.

TheAceOfHearts2• 10 years ago

Am I the only one that finds its kinda weird that they'd announce a UI/UX framework without a live previews? That's really one of the killer features of the web, that you can show stuff off without installing anything.

FreakyT• 10 years ago

Agreed, all the way at the bottom they almost seem to have a link to examples, but then it turns out that it's just a repo of examples that you can clone and serve yourself.

It definitely seems like they're missing a huge part of what's going to sell this framework without functioning examples online.

Drdrdrq• 10 years ago

On top of that, they have this annoying feature where they list the number of minutes left. Like I want a reminder how much time I am wasting reading some random blog. Not really an example of great UX...

johnjuuljensen• 10 years ago

Has anyone used Aurelia with succes?

I'm currently looking into what our next client side framework should be and I have a really good feeling about Aurelia. It feels like someone finally got it right. It's the same feeling I had about ServiceStack, which is by far the best web framework I've ever used.

My main criteria is ease of use by backend devs and going by the tutorials I've done so far, that certainly seems to be the case. I am however myself a backend guy and it's quite likely that Aurelia is missing something important or that the niceness breaks down once you cross some complexity threshold, and I can't see that due to my limited experience in that field.

toddwprice• 10 years ago

We are using Aurelia in production, and it is a joy to work in. It gets out of the way as much as possible but does so much for you without you having to do much.

The biggest pain point is the build/deploy step takes some work to perfect, but this is being worked on by the community and is a pain for every front-end SPA framework.

As far as ease of use by backend devs, I'm not sure what you mean as the back end can be anything you want. We use a Node.js API for our back end, but use whatever you want to create a REST service and Aurelia will consume it just fine.

chadporter• 10 years ago

We've been using Aurelia in production since early beta. Have a half dozen live projects in it now, including Cordova apps (but not Electron apps).

It's been great. Very easy to work with and good performance these days. The best part IMO is that you don't really get sucked into an Aurelia-or-nothing situation. It's not hard to work with other techs right inside your Aurelia app. We often had a dev that was less familiar with the possibilities in Aurelia do stuff using technologies they already knew, and then we'd convert it to use Aurelia methods later after the feature was proven.

Most of the gotchas I've run across are related to observing arrays. By default some array mutations aren't caught. There are ways around this by manually importing the BindingEngine and setting up a subscription, or using @observable on a property, but before you figure that out array observation is a bit vexing. It's not that these other methods are hard, it's that you have an expectation of collection observations and the way it works (largely for performance reasons) doesn't mesh with that.

It does pay to have someone familiar with Aurelia and not all dabblers. We do a good bit of advanced stuff like dynamically generating bindings based on conditions defined in data (e.g. show/hide this form field if these other arbitrary form fields have these arbitrary values, which can be changed by the user, and automatically rebind to the new fields when conditions are changed). Doable if you use some of the more core Aurelia features, but not really something you can do with just the basic surface APIs.

Aurelia or not, all of our architecture is front end + app-agnostic API. Backend devs don't need to give a crap about Aurelia if they don't want. If you mean "is it easy for backend devs to do front end work using this?", I don't know because we don't have any pure backend guys for me to use for reference.

Aurelia UX

Related Stories