search

open-austin / open-data-progress-report

http://open-austin.github.io/open-data-progress-report/
7 stars 14 forks source link

prepare for UX testing #12

Open haileypate opened 9 years ago

haileypate commented 9 years ago

the City's web services team has staged the progress report as an iframe embedded in the standard austintexas.gov template. access to demo page is pending... so here's the screen shot for now https://drive.google.com/open?id=0ByH6oExoXJ0KMWl1RG5QSnp2VFk

@mateoclarke Can you tell me about what testers will need in order to evaluate the UX? Need help knowing exactly what to ask for from the web services team.

mateoclarke commented 9 years ago

Hey @haileypate, I don't understand the question. Who are the "testers" that would evaluate the UX? Are you asking what's the best way to test the embedded version before your team pushes it live?

haileypate commented 9 years ago

Hmm.. maybe a part of this is me not knowing enough about how page styles and iframe styles co-mingle, if at all.

On the launch checklist, I like this part:

Test on various mobile devices:

scrolling is easy nav bar works hoverable things are tappable charts/maps look ok

So I'm trying to figure out what steps I need to take to make this testing possible. If this is something that COA web services can test and fix on its own, then I can probably take this on.

If y'all want/need to collaborate on the testing, I want to help make that happen... so that would mean we'd need to test the files in the screenshot (currently on an internal City server) in a place that's accessible to non-COA staff, right?

mateoclarke commented 9 years ago

Those are just some guidelines that probably don't apply here. There is no nav bar, nothing is tappable besides basic links, no maps.

That leaves scrolling and how the chart looks on mobile. And if the CTM devs are happy with the current embedded format, they should move forward. I wouldn't let mobile responsiveness hold it back because we still don't know what layout this will be embedded in. Though it seems like your team might since you closed Issue #4?

It appears Alex has this staged from the screenshots. The code is a resource to be used freely within the public domain. If he has questions about anything, I'd be happy to help make his life easier. As a first priority, we'd like to include more icons, and that issue is open (Issue #7) and folks like @carissamelanson are contributing. If there are any other priorities, they should be opened as Issues.

I'd love to include some reference to the newly liberated datasets referenced in Issue #5 :wink:.

( :basketball: in your court... )