Settings and activity
5 results found
-
27 votes
Shawn Kelshaw
supported this idea
·
-
96 votes
An error occurred while saving the comment -
1 voteShawn Kelshaw
shared this idea
·
-
4 votes
An error occurred while saving the comment Shawn Kelshaw
commented
I can respect your position. As Product you need to constantly evaluate the value-add opp vs. the overhead (cost and time) to support and produce features. As designers we have to be familiar with device limitations and Alexa Show (or whatever device/generation) should be no different. The exercise that led me to report this issue was essentially exploratory despite presenting it as a design concept for a legit client. I've learned a lot through the exercise and appreciate your dialog. You guys are doing well and I for one appreciate the effort of the entire team.
An error occurred while saving the comment Shawn Kelshaw
commented
Thanks for the reply and information Mark. I think some of my disconnect also extends to the "previewing" a prototype inside XD. You can include a space for the voice playback and preview the experience inside XD just fine.
Suggestion:
XD previewing should mimic device rules.Dependencies:
Adobe XD would need user to identify targeted device
Adoeb XD would need to stay current with device rules from one generation release to the nextOn a side note:
I've noticed tween animations do not display on the Alexa Show. Is this an intentional limitation on the device itself, a bug or an XD feature to be released later on?Thanks again Mark.
Shawn Kelshaw
shared this idea
·
-
851 votesShawn Kelshaw
supported this idea
·
An error occurred while saving the comment Shawn Kelshaw
commented
As the XD team considers the viability of this feature request, I would strongly urge them to take a look at the standards (geometric shapes and their definitions of use) as set by Jesse James Garrett and his visual vocabulary.
http://www.jjg.net/ia/visvocab/
Axure has a native "Flow" library that contains JJG's shapes library (+ others). Axure's "Flow/Connector" mode allows the author to create flow models (IA) whereby shapes can be drug around the stage as necessary and without breaking connector paths.
It would be great to see XD's take on this feature... but please... there's no reason to create a whole new definition of how geometric shapes should be used to articulate a flow... that work has been done already by Jesse.
Adobe has run out of revenue stream ideas and is forcing users to consume cloud space. Depending upon your plan, you could have up to 100GB of cloud storage. They are attempting to drive sharing and collaboration and the only way to deliver on that functionality is to sacrifice the convenience of linking local libraries and assets; otherwise, they will have a different set of customer complaints... like: "why can so-and-so comment on my designs?" Answer: "because your files aren't in the cloud." It's a win/win for them. They drive activity (through sharing and collaboration), they increase revenue (cause eventually you're likely to need more space) and they remove an entire set of complaints and support challenges of designers that would otherwise work locally and still want to "share and collaborate" from time-to-time... "as a user, I want to work with local files..." Can you sayyyy... backlog?