When working with third-party components, there are times when you need to add missing functionality. Let’s take, for example, a custom checkbox component. You need this component, but the problem is that it does not support accessibility. What you are not going to do is to change the source code, so how can we overcome the problem in the Angular way?
Some of the most annoying production bugs we encounter with AngularJS apps are the injection errors: Unknown provider: tProvider <- t. That error message is actually Angular trying to tell us that it doesn’t know where to inject t from, yet of course our code doesn’t have an injectable dependency called t.
We run into startup businesses using payment processing applications like Square all the time. If you're unfamiliar with these applications, they are credit card processors, whereby the customer signs their name to validate the transaction. This signature ends up in your email receipt and is also likely to be sent to the processing servers for storage. So how does one accept signatures within their Android and iOS mobile application?