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.
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.