Re:Show HN: AiDee – a open source micro-framework for Touch ...
by bouke on Tuesday February 25, 2020 @01:11AM
(#22411266)
Indeed. The readme itself says it “aims to be a simple example of Apple's not-so-new LocalAuthentication API usage“. So this is more like a “swifty wrapper” around LAContext[0].
Re:Show HN: AiDee – a open source micro-framework for Touch ...
by hboon on Tuesday February 25, 2020 @01:27AM
(#22411312)
Yeah. I skimmed through the code. Seems unnecessarily. It does wrap it to run in the main thread, which can be useful.
I've found that more often than not, saving a few lines of code in too many places in the codebase can almost introduce a new dialect of the language for the team and newcomers to the team to learn and maintain.
I thank the author for sharing and taking the time and effort to do this and it seems like others are finding it useful, so it's all good.
Re:Show HN: AiDee – a open source micro-framework for Touch ...
by aiFigueiredo on Tuesday February 25, 2020 @05:47AM
(#22412188)
Thank you so much for your feedback. I was unsure how to properly name this, but maybe Biometrics Wrapper would have been better.
Regarding LAContext, the only difference is that aiDee adds an extra layer of abstraction with a clean and simple public API (e.g. biometricAuth.authenticateUser(...) instead of context.evaluatePolicy(...)).
If I had a company where I'd need to implement this in 10 different apps, I think I would do something like aiDee.
[0]: https://github.com/aiFigueiredo/aiDee/blob/029fcd9c9ca8c3242...
I've found that more often than not, saving a few lines of code in too many places in the codebase can almost introduce a new dialect of the language for the team and newcomers to the team to learn and maintain.
I thank the author for sharing and taking the time and effort to do this and it seems like others are finding it useful, so it's all good.
Regarding LAContext, the only difference is that aiDee adds an extra layer of abstraction with a clean and simple public API (e.g. biometricAuth.authenticateUser(...) instead of context.evaluatePolicy(...)).
If I had a company where I'd need to implement this in 10 different apps, I think I would do something like aiDee.