search

Azure-Samples / MyDriving

Building IoT or Mobile solutions are fun and exciting. This year for Build, we wanted to show the amazing scenarios that can come together when these two are combined. So, we went and developed a sample application. MyDriving uses a wide range of Azure services to process and analyze car telemetry data for both real-time insights and long-term patterns and trends. The following features are supported in the current version of the mobile app.
http://azure.com/mydriving
MIT License
388 stars 279 forks source link

documentation changes #569

Open praveenbarli opened 8 years ago

praveenbarli commented 8 years ago

1) in \scripts\Readme.md In section: Service Fabric cluster configuration (optional) after connecting to azure subscription , the below command to set the context helped me in getting step 3 run successfully. powershell cmd: Set-AzureRmContext - SubscriptionId

2) In Deployment article ( https://azure.microsoft.com/en-us/documentation/articles/iot-solution-build-system/) for mobile app to work properly : we should sign on Mobile app with Microsoft account. This is mentioned in reference guild but not in the web article. https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-how-to-configure-microsoft-authentication/ 3) For Mobile App Service (backend API) SSL should be configured which could be done in the portal . This is missing in the above deployment web article. 4) In mobile app we got to create our own pfx file (certificate) and create a package before deploying to hockey app. A link to create certificate would help (https://msdn.microsoft.com/en-us/library/ff699202.aspx)

PiDiBi commented 8 years ago

thx, will look at it, it would be helpful to do Pull Request ... David

kevingbb commented 8 years ago

Some additional comments/feedback on documentation updates when building the Mobile App for an environment deployed into a new Subscription:

  1. The need to change the DefaultMobileServiceUrl for the back-end connectivity is not intuitive or easy to find. Once you find the right file it is a simple copy and paste.
  2. The need to change the DefaultHostName setting for the IoT Hub is not intuitive.
  3. The Bing API Key is there so that is good.
  4. The need for a Google Maps API Key to be able to view the map when compiling for Android devices is not intuitive.

In addition to the Mobile Apps, it would be good to highlight the need to setup the PowerBISink for the Streaming Analytics jobs even if the automated deployment is used.

298029lkk commented 7 years ago

Cool ,666666