OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

arip message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: updated meeting minutes from ARIP call 9/22/2016 - Huawei interview


Hi,

 

Thanks Farhad and Clark for the corrections. The minutes have been updated below in pink…

 

Thanks!

Sally Martir

NA Documentation Project Manager

Huawei Technologies USA

5340 Legacy Drive, Suite 175, 238N

Plano, TX 75024

work: 469-277-5854

cell: 469-939-1504

email: sally.martir@huawei.com

https://www.facebook.com/huaweidocumentationexpress

 

From: sally martir
Sent: Thursday, September 22, 2016 4:09 PM
To: arip@lists.oasis-open.org
Cc: Rhonda Truitt; farhad patel
Subject: meeting minutes from ARIP call 9/22/2016 - Huawei interview

 

Meeting Minutes for ARIP TC 9/22/2016

 

Attendees

Rhonda Truitt

Farhad Patel

Clark Dodsworth

Sally Martir

David Filip

 

Agenda

Interview Rhonda Truitt and Farhad Patel about Huawei’s AR experience.

 

OASIS: What are the main topics that you can speak on today?

RT & FP: Best Practices and Pain Points

 

Clark, OASIS: We should keep a roadmap of things we may want to consider in future pilots.

We haven’t had to deal with commands or gestures.

Floating text to tap the window and move it around.

This should be put on the roadmap for future development.

 

OASIS: Tell us about your latest projects.

RT & FP: At Huawei we just completed:

4 experiences using object recognition

1 using interactive print – interactive, launch video or animations, zoom in, zoom out, email, share, wii chat, facebook, rotate

 

OASIS: What are some examples of the interactive print?

RT & FP: The view is of the device and you click on different parts of the component, zoom in zoom out, move the table farther away and closer, increase and decrease the bandwidth, slider bar, change the distance and the components to show the differences.

 

OASIS: Can you show a demo?

RT & FP: The video demo of a Super Dual Band shows:

·         Object recognition, on the piece of paper, linking to the Huawei portal,

·         Completed animations

·         Slider feature can show and change the distance and compare 3 different possible solutions

·         Slider can increase and decrease

·         Tablet can move closer and farther from the paper

·         The intended viewers are high-level decision makers, sales, and marketing folks for conference booths.

 

We are using the video right now to grab attention from mangers and funding deciders.

At the last Shanghai Wireless User Group, the documentation booth with the AR demo had the most traffic.

 

OASIS: Was there any discussion about voice navigations?

RT & FP: No, it never came up.

 

OASIS: How many users got to try it?

RT & FP: About 800 people

 

OASIS: Was there any information gathering?

RT & FP: Comments were documented. Comments like wow this is great! When can we get it?

 

Clark’s feedback: Ask, how can you use this in your organization? Use interns to do the questioning.

 

OASIS: What was the topic of the other demos?

RT & FP: Object recognition, post recognition checklist. It’s an outdoor checklist. Post installation audit. (We watched another demo video). Object recognition and digital overlays.

 

Clark’s feedback: Use real-looking graphics as much as possibleIdentify the colored wires. Make the wire colors brighter.  Introduce graphic overlay elements unambiguously. Then position them for their task. This enables a new user to know what the graphic overlay is and is for, without needing to re-aim his or her cognition from the task at hand. Use visual or audio cues to signal the new on-screen item.

 

Methods for introducing graphic overlay elements:

                1) Attach a brief, sharp but not loud audio cue to the visual pop-on event. 

 

                2) Slide the graphic item on-screen, from one side of the screen, slowing it as it reaches the task position. The motion should be a linear, unambiguously not manual.

 

                3) “Dissolve-on” This would be called ‘magical looking’ in that there’s a (reusable) bit of ‘cloud-esque' visual effect from which any graphic element can seem to coalesce. This method of bringing the graphic element onscreen should be accompanied by an audio cue, also, for the same reason as above; bringing the user’s attention to the new element, and in sync with the appearance of the text at the bottom of the screen that describes the intended task.

 

                4) Either with or without any of the above methods: Build in a slow visual pulse (~2 or 3 peaks per second) of the graphic itself, so the graphic is visually behaving in a manner that isn’t real. Then, as soon as it moves across the screen to its proper position, the pulse stops. The pulse should be only just visible enough to be noticed, not so colorful or so bright that it distracts the user any more than necessary for that ‘moment of recognition’ to happen.

 

                5) When needed, apply a traveling semi-transparent overlay behind any graphical overlays to ensure that they stand out well against any contrast portion of the device that is being explained. This applies to text, and text color in general should be managed to always have good contract. 

 

                6) When a graphic item is introduced, and the instructional text at bottom of the screen that describes the action to be done with the item represented by the graphical item, it can often be helpful to put in an arrow from the text to the item being described, and immediately thereafter, from the verb in the text to the place where the item is being positioned/adjusted/removed, etc. Brief exposures of the arrows, in order to not clutter the screen. 

 

OASIS: What are best practices that you have learned?

RT & FP: Use cases are of utmost importance from the start. There were several times where changes had to be made mid-project because it wasn’t working.

 

Ask these questions to help determine the importance of the use case:

·         What is the burning problem or need that AR could solve?

·         Is the product outdoors?

·         Do you have the 3D assets? Without the assets, it’s not possible to go forward with the project.

·         Do you have the budget?

·         Is the product fairly stable? You can’t work on something brand new which will evolve too quickly, risk not having CAD drawings, or may not be picked up by a customer.

·         Is the equipment track-able? You can’t have any shiny surfaces for the object recognition to work well.

·         If it’s a complex procedure, it might be better for AR. And the opposite, don’t waste your money on simple procedures.

 

OASIS: What were lessons learned?

RT & FP:

·         Was talked into doing a glasses experience. Had to start over and change field of view.

·         Also, these items (from best practices)…

·         Outdoor lightning is difficult to control, making projects outdoors very difficult to replicate and control.

·         Without 3D assets, it’s not possible to go forward with the project.

·         It’s too difficult to work on a brand new project which will evolve too quickly, risk not having CAD drawings, or may not be picked up by a customer.

·         You can’t track if you have any shiny surfaces. The object recognition does not work well.

·         Don’t waste your money on simple procedures.

·         Storyboarding needs to be robust, precise, and marked out every step-by-step.

·         Feasibility study based on all lessons learned items (and more) needs to be very focused.

·         Get everything documented, reviewed, and approved before beginning the process.

·         Avoid scope creep

·         Use cases must be rock solid and people need the authority to speak up quickly if they see any issues.

 

OASIS: Did you engage collaborative groups (other services departments)?

RT & FP: Yes, training, GTAS, remote support possibilities

 

OASIS: Are there any differences in iOS?

RT & FP: Developers were more resistant to work on iOS. They preferred Android.

 

Clarke’s feedback:

·         Make sure that line producers have good data for budget and the authority to manage any unplanned scope creep.

 

Thanks!

Sally Martir

NA Documentation Project Manager

Huawei Technologies USA

5340 Legacy Drive, Suite 175, 238N

Plano, TX 75024

work: 469-277-5854

cell: 469-939-1504

email: sally.martir@huawei.com

https://www.facebook.com/huaweidocumentationexpress

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]