Технология ibeacon в платежных решениях для торговых компаний
•Descargar como PPTX, PDF•
2 recomendaciones•764 vistas
Применение технологии ibeacon в платежных решениях для мобильных приложений (iphone/android). Кроссплатформенное решение с использованием Azure и Xamarin.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (9)
Similar a Технология ibeacon в платежных решениях для торговых компаний
Similar a Технология ibeacon в платежных решениях для торговых компаний (20)
Технология ibeacon в платежных решениях для торговых компаний
- 1. DevCon 2015 developers productivity platform
- 2. Денис Кретов, Технический директор, Notissimus Технология iBeacon в платежных решениях. Кроссплатформенное решение с использованием Azure и Xamarin.
- 3. DevCon 2015 #MSDevCon Все, что вы хотели знать о iBeacon, но боялись спросить. Часть 1. Обзор технологии iBeacon.
- 4. • “Beacon”(англ.) – радиомаяк • Основа Bluetooth Low Energy • Часть Bluetooth 4.0 • “iBeacon”: стандарт и бренд Apple iBeacon – что за зверь?
- 5. • Низкое энергопотребление • Радиус вещания – 30 метров в хороших условиях • Частота вещания 100 мс • Передаваемая информация: Идентификатор (UUID, Major, Minor) и эталонный уровень сигнала Характеристики
- 6. • Смартфон должен поддерживать BLE • iOS 7+, Android 4.3+, WinPhone 10 • На телефоне должен быть включен Bluetooth Ограничения.
- 7. • В непосредственной близости(“Immediate”), до 50 см • Близко(“Near”), до 2м • Далеко (“Far”), до 30 м • Неизвестно (“Unknown”) Оценка близости.
- 8. • Телефон как маяк • Estimote • Kontakt.io • BlueBar • RedBear • другие Производители.
- 9. • Торговые сети (PayPal, Starbucks) • Навигация (аэропорты) • Временные социальные сети • Умный дом • Электронные гиды в музеях • Контроль процессов (частота, время нахождения сотрудника в зоне) Применение технологии.
- 11. DevCon 2015 #MSDevCon Мобильное решение с использованием iBeacon, Azure, Xamarin и Яндекс.Денег Часть 2. Создаем конкурента решению PayPal
- 13. Схема решения. Часть II. Купить
- 14. • Bluetooth Low Energy • Xamarin • Azure • API Яндекс.Денег Технологии.
- 15. Xamarin.Кроссплатформенность. Apple Android WinPhone Специфичный для каждой платформы код на c#
- 16. • База данных проекта • Единый API для связи между базой данных и мобильными приложениями • Отправка Push-уведомлений Azure.
- 17. Azure.Push. APNs Azure Notification Hub iOS WNS GSM Windows Phone GoogleAndroid
- 18. • Встроенные покупки (Native) • Яндекс.Деньги (WebView) • PayPal (Native) • Платежные шлюзы (Native) • Платежные аггрегаторы (WebView) • API банка (Native) Варианты оплаты в приложениях. Lдругие
- 19. iBeacon в WinPhone 10. Package.appxmanifest <Capabilities> <m2:DeviceCapability Name="bluetooth.genericAttributeProfile"> <m2:Device Id="any"> <m2:Function Type="serviceId:ID beacon"/></m2:Device> </m2:DeviceCapability></Capabilities> Page.xaml.cs protected override async void OnNavigatedTo(NavigationEventArgs e) { foreach (DeviceInformation di in await DeviceInformation.FindAllAsync(BluetoothLEDevice.GetDeviceSelector())){ BluetoothLEDevice bluetoothLEDevice = await BluetoothLEDevice.FromIdAsync(di.Id); } }
- 20. DevCon 2015 #MSDevCon DEMO BluetoothLowEnergy в WinPhone 10.
- 21. Денис Кретов Технический директор, Notissimus kretov.d@notissimus.com Технология iBeacon в платежных решениях. Кроссплатформенное решение с использованием Azure и Xamarin.
- 22. ©2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Notas del editor
- Slide Objectives: Explain the three established industry terms for cloud services Speaker Notes: There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service. Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform. Notes: There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services. The industry has defined three categories of services: IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another.
- Slide Objectives: Explain the three established industry terms for cloud services Speaker Notes: There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service. Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform. Notes: There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services. The industry has defined three categories of services: IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another.