-
What would really make you excited- Round 2
-
I think VR is just fade and will die in a year or two.
-
My guess is that Apple don’t like feature requests as much as they like getting insights into how you work. The ProApps team like stories.
They like each feature request to come with a story showing how it would change your day to day life. “I often have these kind of tasks. I have to do this in Final Cut. It would save me a great deal of time if the task went this way.”
‘Seamless integration with XX’ is a clear request, but if you are more specific, it would be more useful. How would it work with Motion or Logic – in combination with multi-editor collaboration for example?
This way of giving Apple insight means they can compare your stories with people in different markets.
10.3 was about the answering requests made by people with complex workflows. I expect the next major update to be about the majority of Final Cut users. The trick is to come up with stories that could apply to more than 40% of users, and new stories that help them and you.
@Alex4D
-
[Alex Gollner] “My guess is that Apple don’t like feature requests as much as they like getting insights into how you work. The ProApps team like stories.”
I think maybe a better way to describe that would be to say they want to know what is the problem you are trying to solve – rather than asking for a specific feature or function. They might come up with a totally different way of doing something (Lanes) if they aren’t trying to chase features (a track-based mixer). Yet it solves the core problem.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Alex Gollner] “The ProApps team like stories.
They like each feature request to come with a story showing how it would change your day to day life. “I often have these kind of tasks. I have to do this in Final Cut. It would save me a great deal of time if the task went this way.””
If this is really how they prioritize and prefer to get feedback they should make that clear on their feedback page. And for complex workflows/requests, it can be hard to tell your story (the problem) and your proposed solution when they limit you to 800 characters (which is the limit I hit on their feedback page when submitting requests).
Maybe I’ll submit a request asking for a higher character limit on the feedback page. 🙂
—————-
Michael Hancock
Editor -
[Michael Hancock] “If this is really how they prioritize and prefer to get feedback they should make that clear on their feedback page.”
Lots of developers think in terms of user stories. They’re a great way to present feature requests or bug reports to almost anyone.
Here’s a good introductory article:
https://www.mountaingoatsoftware.com/agile/user-storiesWalter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
That article is great. Thanks.
When I submit feedback on an app, I’ve always submitted it under two headings:
PROBLEM: This is the problem I am having.
PROPOSED SOLUTION: Here is how I think it could be solved, or what I need to happen for it to no longer be a problem.I’ll have to think about how to better submit concise but clear stories.
—————-
Michael Hancock
Editor -
[Walter Soyka] “Lots of developers think in terms of user stories. “
It’s obviously good practice for developers, but that’s not a reason for users to have to think in terms of user stories, or for the developer to demand a user story from the user.
Simon Ubsdell
tokyo productions
hawaiki -
[Alex Gollner] “My guess is that Apple don’t like feature requests as much as they like getting insights into how you work. The ProApps team like stories.”
To be blunt about this, I think this approach is both rude and silly.
Because they can’t condescend to listen properly their products are the weaker for it.
There’s no such thing as a bad idea and anyone can have good ideas. It’s sheer vanity to think you have a monopoly on good ideas.
Simon Ubsdell
tokyo productions
hawaiki -
What I don’t get though, is that Apple specifically employs folks to sift through and collate the feedback submissions for common feature requests, reproducible bugs, etc. Isn’t it their job to combine this input into a development strategy so that the most number of people get a solution that works for them? I get that it’s pointless to create a feedback post with a list of 50 items on a wish list. However, specific 1-item/1-post submissions should be pretty easy to build into a database. AFAIK, they do that.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “What I don’t get though, is that Apple specifically employs folks to sift through and collate the feedback submissions for common feature requests, reproducible bugs, etc. “
They collect it, sift it, collate it.
And then put it in the bin.
Simon Ubsdell
tokyo productions
hawaiki
Reply to this Discussion! Login or Sign Up