Hi Dave,
My name is Barton Fiske and I'm the new PM for CreoView - I joined PTC in April of 2014, replacing Madhavi Ramesh. This same question has been asked and recently addressed on the LinkedIn Creo View group, and for which I've provided some updates on where we're at with mobile platform development.
Below is the excerpt of my reply-post to the original thread:
From: Barton Fiske
Director of Visualization Solutions Management at PTC
Hello - please allow me to introduce myself as I've not previously posted in this thread. My name is Barton Fiske ( https://www.linkedin.com/in/bartonfiske ) and following Madhavi's departure at the start of 2014 from PTC to found her company Punditas, I'm very pleased to be joining PTC as the new solution director for Enterprise Validation and Review - which includes product management responsibilities for Creo View MCAD.
At this year's PTC Live Global in Boston last June, during the PTC/Customer joint Technical Committee sessions, this topic was also raised - specifically about Android support. As Madhavi indicated, it is on our list of potential future projects. What I can state at this time as we're clear on the demand from the customer base and community about wanting an Android version of the current Creo View iOS mobile app. What we are working on at the moment is to scope how much effort this would require, and what is the right feature/function balance for a mobile platform implementation?
Moreover, we also realize it is unlikely that a first generation mobile app out of the gate will satisfy everyone's needs - given the higly variable roles and responsibilities of people that need a solution such as Creo View.
One possibility we're evaluating is not necessarily to attempt to deliver an end/all be/all mobile app, rather an API toolkit and (possibly) role based reference apps that would allow customers and the mobile app developer community to develop their own apps and more rapidly serve the above needs - and with more precision between what a specific class of user needs, and what apps on these platforms can do well.
It's also clear that when considering the mobile device space for 3d/2d viewing/markup applications, there are signficant usability considerations when developing for a tablet vs. a smart-phone (or even a watch/micro-mobile) - and then further consider there are technically 3 viable OS platforms (Android, iOS & Microsoft) for each class of device.
In this regard, what might on the surface seem a simple and obvious choice becomes more complex when perhaps at most one or two of those choices will ultimately resonate well with the user base and succeed in terms of adoption and demand.
I realize the above doesn't answer the question: "When Android?" so to at least address that, there is no date at this time. I invite anyone who would like to discuss this in greater detail to email me @ -.
Thanks to all above for the comments to date and your continued interest in this topic.
Barton Fiske
