I want to entertain the possibility of paying (or chipping in with others) for the creation of an open source best practices Enyo 2.7 application focused on integrating Enyo with Loopback. It would need to address authentication, dealing with related data, and local storage syncing. It would also need to be viable for legacy webOS and luneOS. I find the current examples of backend interaction seriously lacking for 2.7 and want to see if there is some way that a more robust example could be created. I was thinking that it might provide the most impact to attack an existing Loopback example, see: Enyo Loopback SDK?
and More 2.7 data examples please
, but I am also open to other ideas. My direct email is already published on our website, so I don't see any problem including it here - email@example.com - but I'd also like replies to this thread if folks have ideas, input, money to pony-up, etc. If there are any existing examples of connecting Enyo 2.7 to multiple API endpoints (wouldn't need to be Loopback specifically) and dealing with committing related data that I have somehow missed or that anyone is willing to share, that might be enough for me and might avoid this (probably too expensive for me) project.