'Keep driving, need more points' is not a good way to inform the user that he did not move during the trip. The purpose of the application is not to get points.
Change the dialog to inform the user that he did not moved at all during the trip. Give three options:

• keep driving
• save the trip anyway
• discard the trip

We need to have master MyDriving solution for all the projects

Proposed Structure (Solution Folders in Master SLN)

• Mobile App (Xamarin + UWP)
• Services (All server side code and projects)
• Scripts (Scripts)
• ARM Templates (Contains ARM templates files and metadata)
• App Service (Contains mobile app backend)

If you use the 4 inch emulator, you'll notice that the calculations pane on the current trip\past trip screens is cutoff.

When we are logging in UWP with FB/AD after successful login it takes a while to show the second screen. During this time we get a splash of the same login screen which looks spooky. We need to make sure we show a blank screen or busy waiting screen.

Every hard brake I was coming to this screen. Is there any way we can configure this ?

It shows N/A gallons, 0 miles, 0s durations and N/A engine load.

Currently Android and IOS implement a summary image which is extracted from Bing Maps. We need similar functionality in UWP too.

I launched the app and forgot it for a while (phone was auto-locked). When I tried to unlock the phone, the phone was hung.
I saw the message in the output window

2016-03-11 10:08:14.554 MyTripsiOS[1902:664013] ** -[UIApplication _handleNonLaunchSpecificActions:forScene:withTransitionContext:completion:] ** unhandled action -> <FBSSceneSnapshotAction: 0x146cc8510> {
handler = remote;
info = <BSSettings: 0x144e9c720> {
(1) = 5;
};
}

When we provision the device using this call, it's hanging:

var response = await client.InvokeApiAsync("provision", null, HttpMethod.Post, myParms);

CurrentTrip.xaml.cs

if (!(await viewModel.StopRecordingTrip()))
return;

if StopRecordingTrip returns false you get into an inconsistent situation where you can never stop the trip.

Currently the call to the provision API provided by the mobile service is wrapped in a try-catch. However, we've seen issues where the call to this API hangs seemingly forever with no exception returned.

Not sure why this is occurring, but we should add some timeout logic to more elegantly handle this.

When there are no saved trips, this screen just appears entirely blank. Instead, it should at least show default text saying "No trips have been recorded" or something along those lines. We should confirm with UX exactly what should be displayed here and make sure it's consistent across ios\Android\Winphone.

Currently we are using "Binding" keyword many places to implement data binding. Best practices say that its more performant to replace it with x:bind

Click logout, the app asks you to confirm. Click cancel. --> still logout?

Sometimes when loggin in, client.InvokeApiAsync(
"UserInfo",
System.Net.Http.HttpMethod.Get,
null);

returns null, even though the user/password was correct.
If I try the second time it returns the value.
I got this with MS and Twitter accounts.

Users are going to want to be able to delete a past trip if they want to.

For example, on the past trips list, if user presses and holds a trip show a context menu that allows you to delete.

We may also consider adding a delete button to the past trip detail screen. We may need UX recommendations on this.

Tasks

• Implement View Model Method @jamesmontemagno
• Android UI @jamesmontemagno
• iOS UI @pierceboggan
• Windows UI @nicolehaugen79

I changed the geolocator trigger to await Geolocator.StartListeningAsync(1000, 0);
So
expect: obd read() will be called per second
actual: It is not called for several seconds and then we keep poll it several times continuously.

Proposed Structure

• Docs
• Source
  • IOT
  • Mobile App
  • Azure Services
  • ARM Templates
• Scripts

As discussed with Pierce, looks like our temperature is the temperature of the air surrounding a power supply. Who will care about this temperature?

When this is called on StartRecording in the currentripview model on Android it completely locks and never returns.

This is what we should add to all source files

// Copyright (c) Microsoft Corporation. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for details.

The cancel button is misleading today because it doesn't really cancel - it simply saves the trip with a default name.

We should remove the cancel button and then simply default the name if the user doesn't provide one.

This can be done in the Login View Model to check the connectivity plugin.

In CurrentTripViewModel.cs : 400, we give outside temperature a default value 0. if it is not available, we should keep current value instead of setting it to 0.

Start a trip, don't move, stop the trip. You will see "Keep driving, we need few more points" and the icon turns back to start a trip. Click it, it keeps complaining "Keep driving, we need few more points" but I cannot start a trip.

I've noticed that changing the units to metric from Settings updated the distance but not speed units.
Also Nicole has observed some issues on Part trips screen, units not being updated.

We need to rebrand all assets and UI to reflect myDriving as the new name

Clone repository, open in XS and try building. This wont work since the components are not getting dowloaded. Need to fix this before release.

When testing the Android app on a Nexus 7 device, sometimes when I try to click on the 'replay trip' area it thinks I'm clicking on the map behind it and just moves the map.

It doesn't seem that we are storing our times as UTC - as a result, this is causing issues when calling the Humanize() method (such as in the TimeAgo field on Trip) which relies on the time being in UTC.

For consistency, we should look at using UTC throughout the app.

Just repeat

1. Start a trip
2. Wait for some points
3. Stop the trip and upload the data

two ~ four times

The app may crash with the message
03-14 15:18:51.220 F/art (12827): art/runtime/fault_handler.cc:117] Check failed: !initialized_

In my case, I did not sign-in. I am not sure if this matters.

Via updated specs

Here are some of the fit and finish issues that I saw when I was running the app with Rui.

1. Summary Trip Map Control lacks Start point A and End Point B. Check the Zindex of these MapIcons and increase them to 3 if they are not appearing.
2. UWP app does not have a launch splash icon. We need to fix it and probably use the same Icon used in iOS and Android.
3. UWP LoginScreen SmartCar icon has a mesh art behind it. This is different from Android and IOS. Can you confirm this with Lena and try and use the same icon as Android ? The Android Icon also has SmartTrip written in it.
4. Change the name of the app to MyTrips from MyTrips.UWP.
5. Change the App icon on UWP. Currently the App has default Icon.

The current code that incrementally attempts to connect to an OBD device potentially causes a deadlock if no device is ever found to connect to. Replace this with tokens used to cancel that task.

I just created a 5 minute trip and saved the trip. Saving the trip takes a really long time and once saved when I go back to PastTrip to see the trip, I see that map is horribly jumbled. Need to investigate why this trip is getting jumbled so much.