Mobile UI for review - read-only view to enable review when on-the-run. Editing can be done on a tablet/desktop but review should be possible on a tablet/phone form factor.
Why is it useful, who would benefit from it, how should it work?
ADMIN RESPONSE
Nov 2, 2018
This is now possible using the new Aha! mobile app.
I'd love to be able to have a mobile app; I travel often enough that it isn't convenient for me to pop open my laptop and make updates in the desktop version of Aha. I think it would be fantastic to have an app that would allow you to make updates/add comments to initiatives, add/edit "to do" items, add new features to the parking lot, etc. I was recently traveling for the better part of 2 weeks, and I was really bummed that I couldn't have it all at my fingertips.
I would like to see Ideas Portal available as a Mobile App. For Sales teams and people on the field, it becomes easier to provide feedback while they are talking to customers and prospects instead of waiting to get back to the office and then log it.
While the hamburger menu is dreaded by many, I think Google has proven with their new Material Design that it can be extremely useful. Things like Product Line, Features, Ideas can all be placed inside the hamburger menu.
Mobile means compromising. But since it is the sum of all the features that makes Aha! great, it's very difficult to omit basic functionalities. So what's the solution? My suggestions would be to scrap the different view options. Features for example can be viewed as a board, but also as a details or a list. For mobile you really only need one view.
You would also need to change the orientation of some objects. Take the roadmap for example. On tablets it can remain the same as on desktop, but for smartphones one option would be to make a vertical timeline instead of a horizontal one.
But overall I think it's fairly straightforward to translate the current interface to a mobile experience. Primarily because Aha! has a very clear information architecture and is really easy to navigate. Yes there are a lot of features, but they don't clutter the interface too much. That was my main gripe with Asana: there were just too many features.
I'd love to give some more feedback and do some testing if you guys decided to make a mobile app!
The current web-based mobile support is OK for read-only activities but does not work very well when trying to modify tasks and open new pop-up windows.
Given the nature of the application it will be hard to work with in a mobile form factor (like a Lumia 530) however most people carry mobile phones and should at least be able to review products within aha from their mobile.
For my purposes a read-only, limited range of artifacts should be enough so that I can review things like roadmaps, requirements, plans while on the road/train/taxi.
I'd love to be able to have a mobile app; I travel often enough that it isn't convenient for me to pop open my laptop and make updates in the desktop version of Aha. I think it would be fantastic to have an app that would allow you to make updates/add comments to initiatives, add/edit "to do" items, add new features to the parking lot, etc. I was recently traveling for the better part of 2 weeks, and I was really bummed that I couldn't have it all at my fingertips.
I would like to see Ideas Portal available as a Mobile App. For Sales teams and people on the field, it becomes easier to provide feedback while they are talking to customers and prospects instead of waiting to get back to the office and then log it.
While the hamburger menu is dreaded by many, I think Google has proven with their new Material Design that it can be extremely useful. Things like Product Line, Features, Ideas can all be placed inside the hamburger menu.
Mobile means compromising. But since it is the sum of all the features that makes Aha! great, it's very difficult to omit basic functionalities. So what's the solution? My suggestions would be to scrap the different view options. Features for example can be viewed as a board, but also as a details or a list. For mobile you really only need one view.
You would also need to change the orientation of some objects. Take the roadmap for example. On tablets it can remain the same as on desktop, but for smartphones one option would be to make a vertical timeline instead of a horizontal one.
But overall I think it's fairly straightforward to translate the current interface to a mobile experience. Primarily because Aha! has a very clear information architecture and is really easy to navigate. Yes there are a lot of features, but they don't clutter the interface too much. That was my main gripe with Asana: there were just too many features.
I'd love to give some more feedback and do some testing if you guys decided to make a mobile app!
The current web-based mobile support is OK for read-only activities
but does not work very well when trying to modify tasks and open new pop-up windows.
I strongly vote in favour of a native mobile app!
Given the nature of the application it will be hard to work with in a mobile form factor (like a Lumia 530) however most people carry mobile phones and should at least be able to review products within aha from their mobile.
For my purposes a read-only, limited range of artifacts should be enough so that I can review things like roadmaps, requirements, plans while on the road/train/taxi.