WaveLynx Adds Apple Wallet Support
Apple Wallet opened to mobile access in 2021 but with mandatory use of HID mobile credentials. Now, Wavelynx has released support for Apple Wallet by using an NXP offering: MIFARE 2 GO.
In this report, IPVM examines the following:
- Advantages of MIFARE 2 GO vs. HID Mobile
- Weaknesses of MIFARE 2 GO vs. HID Mobile
- Why WaveLynx Is Using Wallet vs. BLE
- Integration To & Adoption of Apple Wallet Slow
- HID Responds
This report is part of IPVM's Mobile Access coverage, including NFC Is Better Than BLE For Mobile Access, Mobile Access Control Guide, and Ultra-Wideband (UWB), And The Future of Mobile Electronic Access Control with a 2023 Mobile Access Control Shootout coming later this Spring.
*****ynx *** ***** ****** ********* ***
******** **** ***** ******* ******* *** already ********** ***'* ***********,*** ***** ******** ** ********* ***:
*** ******** ********* ** ******** ******* is ******* ***** **** *** ********** needed ** ******* ********* ******* *** employee ***** ** ***** ******.
***** ****** *********** **** ******** ******** development ** ****** ****, ***** ********'* ******* ***, ******* **** ** * ********** company, *.*., ** ****** ******* ******, hospitality *******, ** ******** *******. ** is *** **** *** ******* *********** except *** **** ********** (*** **** VIPs, ***********, ***.)
Integration ** & ******** ** ***** ****** ****
***** ***** ********* *+ ****** ***, we *** ***** ** ***** ****** providers (***********,************,*****- ******** ***** *** ******) **** have **** ***** ****** ****** ********* to ***-*****, ***** **** * *** property ********** ********* (*.*.;*********** *************** ***** ***,*** ********** *-****).
****** *** ** ******* *********** **** to ****** ***** **** *** * factor, *** ** *** ** *** Apple ********* *******, ***** *** **** described ** '********.' *** *******, *** testing ** *****'* ******** **** ***** Wallet *** **** ** ******* *** 6+ ****** *** ** ***** ******** Apple ******/*** ***** *** *******. *******, WaveLynx **** ***** ********* ****** *** completed *** ***** ***.
********'* (***) ****** ****** ****** ******* advantages **** ***** ******** *** ****** solution, ********* ** ******** ** ****** the ***** ** **** ** **** an *** ****** ** ****** * door:
**** ******** ***** ** ***** ******, users **** ** **** ** ****** hold ***** ****** ** ***** ***** to * ******** ****** ** ******* tasks **** ********* ****** ***** *** securely ******** ********* ** ********* ******* machines *** **** **** – *********** the ***** **** ** ******* ** app ** ******** ** **** ***** physical ******** *****. **** ******* ****, users ** *** **** ** ****** or **** **** ** ***** ****** to *** ***** ******** ***** — they *** ****** **** ***** ****** to * ******.
******* ********* ** **** **** ** the *****'* ******* ** ****, ** emergency ******* *** ***** *** *** to ****** ***** **** ** *** phone ** ********* *** ******:
** ** ****** ***** ** ** charged, ***** *** ***** *** ***** device ** ****** ***** ****** ** amenity ***** *** ** ** **** hours **** ***** *******.
WaveLynx ********** **. *** ******
********'* ************** ******** * ****** **** *** ********** **** ***** Wallet ***** ***:
***** ****: ** *** ***, ***-*** ****** manufacturers **** *** * ******** ****** to ***** *******, ****** ~$*** ** the ******* *** *** ********* ******** a ****-**** ****, ******* ***'* **** not **** * ******* ****.
******* *************:******* ****** ** * ********** ****** already **** ** **** ******* *** ticketing ************, *** ********** **** *** access ***** ********* ** ******* ** other ***** ************ ********* ******* (*.*., amenities, ****** *******) *** ****** ********** vendors.
WaveLynx ********** **. *** ******
*******, ***** *** ********* ** *** NXP-based ********:
***** *** ***********: *** ****** *** * *********** market ***** ** ***** ******** ******* for ******. ** ******** ******* **** to ** *********** **** ********** *******, market ********** ** ********'* ******* *** be *** ********** ** ******* **** work **** ***** *******.
***'* *** ****** *** ******:*** ** * ************* ************* ******* with * ***** **** ** *** company's ~$**.* ******* ******* ** ****** control. ** ********, *** ****** ** majority ******* ** *** ****** ******* market, *** *** ******* ******** *** commitment ** *** ** **** * small **** ** ***** ******* ******** could ****** **** *** *********** ******** to ** '***-**' ** ***'* ***** wallet *******.
NFC *** *****
***** *********** * ***-******** **** ** NFC, ***** ******, *** *********** ******* using ** *** ******* ***** ***** announcing** ***** ****** ****** ******* ********* ****.
*** ******* ********** ** **** ******* mobile ****** ********* ** **** **** are *** *****, ********* ******** ** mobile ***** ***, ** ****** ** six ****** ****** ******* ***** ** ****** **** *** *** Mobile ******.
******* *** **********, *** *** ** NFC *** ****** ****** *** ************* been ******* ** ***** ******* *** supporting ** - ********** ** ***** ****** ** ****** access*** ******* *** ***.
Apple ****** ******** ** ****** ***********
- ** ****,*** ********* ******* *** ****** **** in ***** ********* * ******* ****** ** **** market *********, ********* *********. (*** *********** was **** ******* ****** ** ****.)
- ***** ** ****,*** ********* ****** ******* ******* ** Apple ******. *******, ************ **** ******* *** did *** ******* ******** ****** ******* until ****.
********-***** ******** *** ********* ********* *** (and *** ********* *** ******) ***** ~2014.
** ****, ******** **** *** ************ decision ** **** *** *** ****** and ********** ********** ** *** ****** DESFire *********. ** ****** ******** ************ and ******** *** * ****** **** demands *** ******* ****** ** **********, and ** **** ** ***** **************** within ** **** *********** ********. ************* on ****** ******* **** **** ** establish *** *** ******** *** ******** adoption.
Traditional ******** ****** ** *** *****
*** *******, *** *** ******* *** mobile ** ******** ******** *****. ******** mobile *** ******* **** *** ***** performance. ** **** ****** *** ******** several *****, ******************** (******* ***):
*** ******* ********** ** ********'* ******* mobile ******** ** **** ** ** BLE *****, *** ***** ************, ** generally ******** ** ****** ***** ***; agreed ** ** *** ****** ****** vendors:*** ** ****** **** *** *** Mobile ******.
HID ********
*** **** **** *** ********* ******* why ****** ***-***** (*.*., ************, ************, commercial **********, ***.) *** *** **** mobile ** ***** ****** ******* ** NXP's ********:
**** ****** * ****** ** ******** to *** *********:
****** *****: **** ** ******** ** be ****-****** ***********, ************ * ****** future ********** ** ******-***** ***********.
****** ******: **** ** ****** ******** Object (***)-*******, ******** *** *****-******* ******** beyond *** **** ********** *** ********** identity **** **** ************ ******.
**********: *** **** ***** ********* ** a ***** ******* **** ** *** readers, *** **** ******* ** *** partners ***-******** ****** ******* **** ********* for *** ***** **** ****** *******, print *******, **** *** **********, ******* access ***. (********* *** ******** ** the ***% *** **** *********** *** Wallet ***********).
HID/Apple ****** ******** *****, *******
*** ********* **** *** ~** users ** ***** ****** ** *** end ** **** *** ****** ****** is "******* *************:"
** *** **** **** ** ** the *** ** **** *** **** added ***** * *** ***** ****. The ******** ** ******* ************* ** we *** **** ***-***** ******* ******* and ********** ** **** **********. *** ecosystem ** ********** *********** ******** ** also ******* ******* ** ****** **** new ***********-******.
IPVM **** ******
**** ** ******** ** **** **** WaveLynx / *** *** *** *************** of ***** ****** **** ****.
**** ********* ******* ** ************* ***** than ***. ******/**********/***** *** *** ********. I've ********* **** ** *** ******.
**'* *** ****** ******** ** *** "device ************* **** *** * ******** module ** ***** *******" ** *** HID ******. *** ****-******* ******/********** ******* (and *** ***** *******) ******* **** this *****-**. **** *** ***-*** *** readers **** **** *************.