`
`“What's New in Core Location ‐ WWDC 2013 ‐ Videos ‐ Apple Dev.mp4”:
`
`This is a great first step at a product. Now, now my friends can, that are trying this app can go to
`a store and get immediately notified that, “Hey, look that you are inside a Jay’s Doughnut
`Shop.” But, one of my friends came back to me and said, “Hey, look. You got that Jay’s
`Doughnut Shop over at Valley Fair Mall and whenever I go inside there and I go by some shoes,
`the result is that my phone starts vibrating because I go by Jay’s Doughnut Shop. So, this is
`relatively annoying. The reality is that users don’t necessarily care that they’re inside a
`Jay’s. They’re usually seeking to interact with your store. And, when they are ready to do that,
`they are perfectly capable of pulling their phone out of their pocket and turning their display on
`and launching the application themselves. So, but we can still speed the process up by letting
`you know when they turned on their phone inside of a store. And, so to do that, there is an
`added property that beacon regions support, which is notifyEntryStateOnDisplay. And, now
`anytime a user turns on their phone inside of my stores, my application will receive a launch
`event. And, of course, we can disable the notifyOnEntry. This is a spurious wake that wasn’t
`really relevant to the user. There is no reason to know that we’ve walked by Jay’s or even
`stepped inside of Jay’s until I’m ready to interact with my phone.
`
`https://developer.apple.com/videos/play/wwdc2013/307/ at [32:40 – 33:59] (accessed Apr. 22, 2021)
`
`BILLJCO
`EX2033 Page 1 of 1
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
