| |
|
October 28, 2010
|
|
2:00 am
|
KnowledgeBishop:
|
In exactly 24 hours, #techcomm will gather for #TCchat session 2: Bring your Mobile Content thoughts! |
|
2:01 am
|
CarlSorvino:
|
RT @KnowledgeBishop: In exactly 24 hours, #techcomm will gather for #TCchat session 2: Bring your Mobile Content thoughts! |
|
2:04 am
|
bwoelk:
|
RT @KnowledgeBishop: In exactly 24 hours, #techcomm will gather for #TCchat session 2: Bring your Mobile Content thoughts! |
|
6:14 am
|
2moroDocs:
|
links coming re mobile content for #tcchat |
|
6:14 am
|
TC_Chat:
|
links coming re mobile content for #tcchat |
|
6:16 am
|
2moroDocs:
|
2010 study of mobile Web trends shows continued explosion of mobile-friendly content #tcchat . http://bit.ly/aGDq6d . #techcomm |
|
6:17 am
|
2moroDocs:
|
5 Can?t-Miss Usability Tips for Mobile Website Designs http://bit.ly/a3wmGk #tcchat |
|
6:18 am
|
2moroDocs:
|
A 3-Step Guide to Usability on the Mobile Web #tcchat . http://bit.ly/2WD1sy |
|
6:21 am
|
2moroDocs:
|
Going Mobile: Designing for Different Screen Sizes #tcchat . http://tc.eserver.org/37617.html |
|
6:23 am
|
2moroDocs:
|
Mobile Accessibility http://www.mobileaccessibility.info/index.cfm . #tcchat |
|
6:23 am
|
2moroDocs:
|
Mobile dev community: http://mobiforge.com/ . #tcchat |
|
6:25 am
|
2moroDocs:
|
Mobile LinkedIn groups: Mobile Content, Mobile Software Development Group http://www.linkedin.com #tcchat |
|
6:26 am
|
2moroDocs:
|
WordPress Plugins #tcchat . http://wordpress.org/extend/plugins/ |
|
6:28 am
|
2moroDocs:
|
I've posted more links re mobile using the #tcchat tag; not repeating all in #techcomm. So take a look! They'll b in paper 2moro. |
|
6:40 am
|
2moroDocs:
|
RT @tc_chat: Mobile Web Initiative: W3C. Specs, info, validation checker, & more. #tcchat http://www.w3.org/Mobile/ |
|
3:00 pm
|
KnowledgeBishop:
|
#Techcomm take note: In exactly one hour, #TCchat session 1 kicks off with a dialog about mobile content! |
|
3:02 pm
|
cfidurauk:
|
RT @KnowledgeBishop: #Techcomm take note: In exactly one hour, #TCchat session 1 kicks off with a dialog about mobile content! |
|
3:08 pm
|
2moroDocs:
|
Many links posted last night & yesterday for 2day's chat. Take a look at the #tcchat tag. #techcomm |
|
3:15 pm
|
2moroDocs:
|
Today's song for #tcchat - our live techcomm event, courtesy @mojoneill http://youtu.be/V92OBNsQgxU Ride of the Valkyries. |
|
3:19 pm
|
tadams_InMind:
|
@2moroDocs WordPress Plugins #tcchat . http://wordpress.org/extend/plugins - haven't seen this before & need to check out! THX |
|
3:20 pm
|
idtp:
|
RT @KnowledgeBishop: #Techcomm take note: In exactly one hour, #TCchat session 1 kicks off with a dialog about mobile content! |
|
3:25 pm
|
tadams_InMind:
|
@2moroDocs Today's song for #tcchat courtesy @mojoneill http://youtu.be/V92OBNsQgxU- Need Starbucks to go w/ music! Nice start 4 the day! |
|
3:27 pm
|
TC_Chat:
|
RT @2morodocs: Many links posted last night & yesterday for 2day's chat. Take a look at the #tcchat tag. |
|
3:28 pm
|
TC_Chat:
|
#tcchat - a live discussion techcomm event about mobile content development starts in 1/2 hour. Join in the discussion! #elearning #stc |
|
3:30 pm
|
ChatSchedule:
|
#tcchat starts at 12 pm EST - RT if you'll be there |
|
3:50 pm
|
ChatSchedule:
|
#tcchat starts at 12 pm EST - RT if you'll be here |
|
4:00 pm
|
2moroDocs:
|
Welcome to today?s #tcchat! Topic: Mobile Content Development #tcchat |
|
4:00 pm
|
TC_Chat:
|
Welcome to today?s #tcchat! Topic: Mobile Content Development #tcchat |
|
4:00 pm
|
2moroDocs:
|
Reminders: please don?t use #techcomm tag. It will overwhelm it. Add #tcchat to your tweets. Thx! Also, no proprietary info! |
|
4:00 pm
|
2moroDocs:
|
Today's song for #tcchat - our live techcomm event, courtesy @mojoneill http://youtu.be/V92OBNsQgxU Ride of the Valkyries. |
|
4:01 pm
|
2moroDocs:
|
Main topics: writing style. Mobile minimalism (mm); usability, hardware, system reqs, #tcchat |
|
4:01 pm
|
2moroDocs:
|
Roll call? Who?s where? #tcchat |
|
4:02 pm
|
2moroDocs:
|
First: mobile use increasing significantly. 2-yr growth of over 2,000 % #tcchat |
|
4:03 pm
|
davkow:
|
Reading tweets in real-time during today's #tcchat organized by @2morodocs. Topic: "Developing Content for Mobile Devices" |
|
4:03 pm
|
2moroDocs:
|
2010 study of mobile Web trends shows continued explosion of mobile-friendly content #tcchat . http://bit.ly/aGDq6d |
|
4:03 pm
|
mojoneill:
|
Chiming in from the great metropolis of Iowa City, IA #tcchat |
|
4:04 pm
|
gdevore:
|
@2moroDocs - Greg DeVore from Blue Mango Learning Systems here for a bit. #tcchat |
|
4:04 pm
|
2moroDocs:
|
Q1: Screen size is small. MM: how much do you cut? What is max no of screens in a series to go through? #tcchat |
|
4:06 pm
|
mojoneill:
|
A1: 7 +/- 2. ;P #tcchat |
|
4:06 pm
|
2moroDocs:
|
Thanks for dropping by, @mojoneill @gdevore @davkow #tcchat |
|
4:06 pm
|
2moroDocs:
|
A1 ex: Mobile Web Best Practices Cards. W3C #tcchat . http://www.w3.org/2010/09/MWABP/ #tcchat |
|
4:07 pm
|
2moroDocs:
|
I'm having some lag time again, it seems. Will keep plugging along. #tcchat |
|
4:07 pm
|
mojoneill:
|
Max number of screens = minimum number required to provide reader with the info s/he needs to accomplish their work.
#tcchat |
|
4:08 pm
|
2moroDocs:
|
@mojoneill With having to minimize content, maybe have to split into more proc so don't have lots of screens? #tcchat |
|
4:09 pm
|
gdevore:
|
We keep 1 task on 1 page that is scrollable. We do our best to keep the tasks small and focused. #tcchat |
|
4:09 pm
|
2moroDocs:
|
Can you all see the cards from W3C? #tcchat |
|
4:10 pm
|
mojoneill:
|
Well, I think the idea of "no more than necessary" is not mobile-specific. Mobile just means lack of adherence = more painful 4 user #tcchat |
|
4:11 pm
|
2moroDocs:
|
@gdevore How much scrolling? #tcchat |
|
4:12 pm
|
robocolumn:
|
@2moroDocs @gdevore I've seen four or more screens scrolled which I think is excessive. Two or three max. #tcchat |
|
4:12 pm
|
2moroDocs:
|
@mojoneill The screen size really is a factor. Comes up a lot in articles I read re dev & usability #tcchat |
|
4:14 pm
|
gdevore:
|
We use images for all of our docs which works very well for mobile web (less reading). Here is an example http://bit.ly/a0KYVU #tcchat |
|
4:15 pm
|
mojoneill:
|
@2moroDocs Agree... but here we get into lots of q's. what's the screen size. What device? What resolution? iPad? Netbook? iPhone. #tcchat |
|
4:16 pm
|
2moroDocs:
|
A1: what abt style changes? How much 2 cut? One idea: http://www.2morodocs.com/tcchat/tcchat-transcripts/ #tcchat |
|
4:16 pm
|
PattyBlount2:
|
@mojoneill Hm. Thought would be dynamic; device adjusts content for own display... #tcchat |
|
4:17 pm
|
2moroDocs:
|
@mojoneill Yes. Hardware critical. Here's an article re diff reqs. #tcchat
http://mobiforge.com/designers/blog/mobile-apps-vs-mobile-web |
|
4:18 pm
|
robocolumn:
|
This discussion could also apply to non-mobile outputs (e.g. aircraft cockpit screens) that have less space than an i-pad #tcchat |
|
4:18 pm
|
ermphd:
|
@PattyBlount2 That what Adobe DM CS5 does with the HTML5 extensions #tcchat |
|
4:18 pm
|
gdevore:
|
We don't worry about customizing stuff for different screen sizes. Most mobile devices handle that pretty well now. #tcchat |
|
4:18 pm
|
2moroDocs:
|
@pattyblount2 There's a test option on the mobile dev site, I think that allows u to test 4 diff devices. #tcchat |
|
4:19 pm
|
gdevore:
|
Much more important than formatting is structuring content for mobile consumption. #tcchat |
|
4:20 pm
|
mojoneill:
|
@PattyBlount2 good point. maybe it is? A lot depends on the app. Try writing for a 42 char. LCD display 4 robotics controller. #tcchat |
|
4:20 pm
|
2moroDocs:
|
The tester is somewhere on this site, I think. http://mobiforge.com/ #tcchat |
|
4:20 pm
|
juliov27612:
|
@2moroDocs Coming in late, but wouldn't it be so much better if the device took care of the display based on the semantics? #tcchat |
|
4:21 pm
|
gdevore:
|
Unless you really mess things up. Like have a left nested folder nav to navigate everything. That really stinks in mobile. #tcchat |
|
4:21 pm
|
ermphd:
|
@2moroDocs Those #WV mobile cards look gr8. Thx Juile! #tcchat |
|
4:21 pm
|
2moroDocs:
|
@gdevore Agreed. Saw that in articles too. Bottom line: web design not equal to mobile. Different animal. #tcchat |
|
4:21 pm
|
PattyBlount2:
|
@gdevore Agree; think mobile users want FAST. Julie's example=ideal. No "clicks", extra verbs. #tcchat |
|
4:22 pm
|
ermphd:
|
@gdevore Good point. The UI needs work but so does the content! #tcchat |
|
4:22 pm
|
2moroDocs:
|
You know, there's a nice iPhone app I downloaded; has drop-down navigation. Nice! It's "Pocket 1st Aid & CPR; Am Heart Assoc #tcchat |
|
4:23 pm
|
2moroDocs:
|
Nice, I think. Hide nav if you can until needed. #tcchat Leaves screen for content. |
|
4:23 pm
|
2moroDocs:
|
@ermphd YW! Other examples on the site. Take a look. #tcchat |
|
4:24 pm
|
mojoneill:
|
RT @2moroDocs: @gdevore Agreed. Saw that in articles too. Bottom line: web design not equal to mobile. Different animal. #tcchat |
|
4:24 pm
|
PattyBlount2:
|
Design for scanning, not reading? #tcchat |
|
4:24 pm
|
ermphd:
|
Perfect. The UI must not get in the way! RT @2moroDocs: Nice, I think. Hide nav if you can until needed. #tcchat Leaves screen for content. |
|
4:24 pm
|
juliov27612:
|
Could any nav. aids for mobile b determined by device based on semantics of content rather than explicitly defined by authors? #tcchat |
|
4:24 pm
|
2moroDocs:
|
@mojoneill I can't remember which article. Have to look thru the list. #tcchat |
|
4:25 pm
|
2moroDocs:
|
@juliov27612 Yep, it would. #tcchat |
|
4:25 pm
|
2moroDocs:
|
Think we should jump into usability. #tcchat |
|
4:25 pm
|
2moroDocs:
|
Q2: What are usability concerns? #tcchat |
|
4:26 pm
|
juliov27612:
|
Paraphrasing @rjacquez Is nave needed on mobile with could search? #tcchat |
|
4:26 pm
|
2moroDocs:
|
A2: what I've seen. Point size. Screen size. How phones used: not just at desk. #tcchat |
|
4:27 pm
|
gdevore:
|
@PattyBlount2 I think all help should be designed for scanning and as little reading as possible. With mobile even more so. #tcchat |
|
4:27 pm
|
PattyBlount2:
|
q2: not able to get "whole story" on small device, just small glimpses. Easy to lose one's place. #tcchat |
|
4:27 pm
|
ermphd:
|
@juliov27612 ?? Not Clear? #tcchat |
|
4:28 pm
|
juliov27612:
|
@2moroDocs Smaller displays require reformatting but default action is to shrink to miniscule sizes. Need to pick better method. #tcchat |
|
4:29 pm
|
gdevore:
|
A2. With mobile need to consider scope vs. detail. Increase scope of content decrease detail. Increase detail decrease scope. #tcchat |
|
4:29 pm
|
juliov27612:
|
@ermphd Why have nav. for mobile at all? Land on page from orig. ref. then allow search. #tcchat |
|
4:29 pm
|
2moroDocs:
|
@juliov27612 Think that hw comes into play. Look at how many options. #tcchat
http://mobiforge.com/designers/blog/mobile-apps-vs-mobile-web |
|
4:29 pm
|
ermphd:
|
@PattyBlount2 Why should we try to tell "whole story" on mobile? Set expectations realistically #tcchat |
|
4:30 pm
|
2moroDocs:
|
@gdevore Seems like that's the tricky part. Perhaps more art than science? Case-by-case? #tcchat |
|
4:30 pm
|
mojoneill:
|
more use of text folding? allow scanning topics and drilling down? #tcchat |
|
4:30 pm
|
ermphd:
|
@juliov27612 Seems a reasonable alternative for some tasks :) #tcchat |
|
4:31 pm
|
juliov27612:
|
@2moroDocs While many options, the hw/sw on device should control the presentation. #tcchat |
|
4:31 pm
|
PattyBlount2:
|
@juliov27612 Not sure about "search" only. What if you don't know exactly what you're looking for? Need something 2 provide context. #tcchat |
|
4:32 pm
|
2moroDocs:
|
@mojoneill Not sure if traditional left column scan works well for scanning. Use bold more, prob. #tcchat. Ex in minute |
|
4:32 pm
|
gdevore:
|
@mojoneill Text folding can make it difficult to share specific parts of a help file with a unique url. Better 2 have separate pages #tcchat |
|
4:32 pm
|
juliov27612:
|
@mojoneill Content then requires added semantics. Key concept. Need more than headings. Key content within body. #tcchat |
|
4:33 pm
|
juliov27612:
|
@PattyBlount2 The search only assumes you arrive at content purposely, so you have idea of context. #tcchat |
|
4:33 pm
|
gdevore:
|
@PattyBlount2 I think good mobile help needs both search and TOC. Just don't create too deep of a hierarchy. Drilling down gets old #tcchat |
|
4:33 pm
|
ermphd:
|
A2 Seems like usuability depends largely on the objectives of the mlearning #TCchat |
|
4:33 pm
|
PattyBlount2:
|
@ermphd warnings or sys. reqs before performing procedure user is reading. I worry they'll miss important stuff like this. #tcchat |
|
4:34 pm
|
ermphd:
|
@gdevore Good point, again focus on objectives for clarity #tcchat |
|
4:35 pm
|
juliov27612:
|
@PattyBlount2 sys reqs. and warnings should be part of target content when searching. Easy to lose in trad. display if not connected #tcchat |
|
4:36 pm
|
2moroDocs:
|
What's really nice is W3C has an ex in mobile format describing the list of what to avoid & what to do. #tcchat Think it's PDF file |
|
4:36 pm
|
ermphd:
|
@PattyBlount2 Agree, but warnings can be tagged & sys req made clear up front #tcchat |
|
4:38 pm
|
2moroDocs:
|
@gdevore Raises other ques. How to highlight links? Use of color impt. 1st aid app uses box around links. Really nice. #tcchat |
|
4:39 pm
|
juliov27612:
|
@2moroDocs Color seems to be diff. to distiinguish. on small screen. Boxes better but not optimum. #tcchat |
|
4:40 pm
|
juliov27612:
|
@2moroDocs Need different link indicator for mobile? #tcchat |
|
4:40 pm
|
PattyBlount2:
|
I have a lot of cramming to do! Use my phone just to make calls. It hasn't got internet access. #tcchat |
|
4:41 pm
|
2moroDocs:
|
@juliov27612 I thought the same, but they really work nicely on this app. Surprised me. #tcchat Heavier box border w/faint color over text. |
|
4:41 pm
|
2moroDocs:
|
Let's jump into hw more again. #tcchat |
|
4:42 pm
|
ermphd:
|
@juliov27612 I wonder if some simple anamation would work for links like flashing light spot #tcchat |
|
4:42 pm
|
juliov27612:
|
@2moroDocs Must be these old eyes. LOL #tcchat |
|
4:42 pm
|
2moroDocs:
|
Q4: How are touchscreens affecting content dev? Ex: do you think abt zooming in more? #tcchat |
|
4:44 pm
|
2moroDocs:
|
@juliov27612 Don't know. Wld be worth looking for more ex. Think we may. Diff reqs. Inline headings; no columns. Color main option? #tcchat |
|
4:44 pm
|
juliov27612:
|
@2moroDocs That shouldn't be an authoring issue. The hw needs to be smart enough to optimize. #tcchat |
|
4:44 pm
|
tadams_InMind:
|
@2moroDocs Q4: How are touchscreens affecting content dev? Ex: do you think abt zooming in more? #tcchat - yes! but it is the future! |
|
4:44 pm
|
2moroDocs:
|
Think that zooming most useful for something like maps. Diff content than a straight proc. #tcchat |
|
4:45 pm
|
juliov27612:
|
@ermphd Simple animation might work for link display. More like a pulsing than flashing. HW should decide. #tcchat |
|
4:45 pm
|
ermphd:
|
@juliov27612 I like it, pulsing links. Good thought! #tcchat |
|
4:45 pm
|
2moroDocs:
|
@pattyblount2 In researching, I found some ways to test mobile w/o having a phone. So, it's possible to try it out. #tcchat |
|
4:46 pm
|
tadams_InMind:
|
@2moroDocs Think that zooming most useful for something like maps. Diff content than a straight proc. #tcchat yes - love when I can expand |
|
4:47 pm
|
juliov27612:
|
@2moroDocs Zooming makes some sense in some content. But design should be left to infrastructure. #tcchat |
|
4:47 pm
|
2moroDocs:
|
@juliov27612 Grt thought. What capabilities 4 each device? If one supports pulse/flash/touchscreen but other doesn't, what do u do? #tcchat |
|
4:48 pm
|
2moroDocs:
|
Now so many devices coming out, we really have to look at capabilities more. Need to watch marketplace. #tcchat |
|
4:48 pm
|
juliov27612:
|
@2moroDocs Remember that color might not be a good choice for entire audience. Definitely need creativity on all fronts. #tcchat |
|
4:48 pm
|
tadams_InMind:
|
@juliov27612 @2moroDocs @2moroDocs Zooming makes some sense But design should be left to infrastructure. #tcchat - but can be limiting! |
|
4:48 pm
|
juliov27612:
|
@2moroDocs Devices should decide what's best for them to display the semantic. #tcchat |
|
4:49 pm
|
2moroDocs:
|
@tadams_inmind Many touchscreens now, though. Also, how does that apply to larger eReaders like iPad? Cont mgmt at play, too #tcchat |
|
4:49 pm
|
juliov27612:
|
@tadams_InMind Only as limiting as the device is limited. Content should suggest, not dictate presentation. #tcchat |
|
4:50 pm
|
ermphd:
|
@2moroDocs It would help to define what the ideal device needs to to for developer/learner #tcchat |
|
4:50 pm
|
2moroDocs:
|
What I'm seeing here are many more ques. Seems we need to watch: hw capabilities now & future. Navigation. Max no of screens 4 proc. #tcchat |
|
4:51 pm
|
juliov27612:
|
Gotta run. Bye #tcchat |
|
4:51 pm
|
ermphd:
|
I have to leave for an Adobe webinar. Good chat, all. I look forward to the transcript and daily. Thx! #TCchat Ciao |
|
4:51 pm
|
tadams_InMind:
|
@2moroDocs @tadams_inmind Many touchscreens , how does that apply to larger eReaders like iPad? #tcchat Agree - love ipad and expand read |
|
4:51 pm
|
PattyBlount2:
|
HW needs to address certain issues. I don't want to design for 'betamax' only to have 'VHS' become the standard. #tcchat |
|
4:52 pm
|
2moroDocs:
|
@juliov27612 If u have a hw limitation for a major device, have to address, I think. #tcchat Affects content design? |
|
4:52 pm
|
2moroDocs:
|
@ermphd Determine a happy medium? What will work on most devices? #tcchat |
|
4:52 pm
|
2moroDocs:
|
Only abt 8 mins left. Any ques to focus on specifically b4 time is up? #tcchat |
|
4:54 pm
|
2moroDocs:
|
@pattyblount2 Agreed. Really have 2 watch what's happening. Look at the article I posted a bit ago that shows how device use chging. #tcchat |
|
4:55 pm
|
2moroDocs:
|
The only things I think will be a certainty: touchscreens. Also screen size. #tcchat |
|
4:56 pm
|
2moroDocs:
|
Just to throw another small-screen item to the mix: screens being developed to wear on clothes, for instance. Also roll-up screens. #tcchat |
|
4:57 pm
|
2moroDocs:
|
Will be other options/hw besides just mobile. So think small screens in general #tcchat |
|
4:58 pm
|
2moroDocs:
|
@tadams_inmind Yep. More capability 4 video, etc on iPad. May be some of same concerns 4 mobile. Video haven't touched on that! #tcchat |
|
4:59 pm
|
content2000:
|
@2moroDocs what about how to decide WHAT content is worth putting on mobile? seems that needs to be very focused on top task items #tcchat |
|
5:00 pm
|
2moroDocs:
|
@ermphd Grt idea. One consideration: kept seeing ref 2 how ppl use mobile. Sitting outside, turning & display chgs. Things like that #tcchat |
|
5:02 pm
|
2moroDocs:
|
Oh my gosh! 10:00! I'll close this officially for now but will stay around 4 afterparty. I think we raised major points 2 consider #tcchat |
|
5:03 pm
|
2moroDocs:
|
@content2000 EXCELLENT point. A first consideration when determining doc strategy. #tcchat |
|
5:03 pm
|
2moroDocs:
|
What criteria does one use to determine what content to use 4 mobile? #tcchat |
|
5:04 pm
|
2moroDocs:
|
Offhand, I think of: audience, how product used, how needed to access #tcchat |
|
5:04 pm
|
2moroDocs:
|
For instance, a scientist working in the field has diff data access/content reqs than an office worker like a writer! #tcchat |
|
5:05 pm
|
juliov27612:
|
@2moroDocs The device should have a default behavior for any semantic it doesn't understand or handle. #tcchat |
|
5:06 pm
|
juliov27612:
|
@PattyBlount2 I liked your videotape analogy. :D #tcchat |
|
5:06 pm
|
2moroDocs:
|
@content2000 Maybe also based on FAQ to support or something like that? #tcchat |
|
5:06 pm
|
2moroDocs:
|
How much based on user input? #tcchat |
|
5:07 pm
|
2moroDocs:
|
Another ques I have: seems that mobile may require more work & time than expected. We all know how hard it can be 2 condense info #tcchat |
|
5:08 pm
|
2moroDocs:
|
@juliov27612 Good point. How do we keep up with all that? With devices chging all the time, how do we know? #tcchat |
|
5:09 pm
|
2moroDocs:
|
Might not know of a new device capability until it launches. Dev secrecy high for hw devices, I think. #tcchat |
|
5:10 pm
|
CharJTF:
|
@2moroDocs Check out @lukew's articles at http://is.gd/goMTH on designing for mobile first. #tcchat |
|
5:10 pm
|
content2000:
|
@2moroDocs agreed - who is using the mobile content is critical, but also how easy the content is to 'parse' in bite-size bits #tcchat |
|
5:11 pm
|
2moroDocs:
|
@charjtf Thanks for the link! #tcchat |
|
5:11 pm
|
content2000:
|
syntax, error message help, etc - make great bite-size searchable content if the mobile app is designed well #tcchat |
|
5:12 pm
|
2moroDocs:
|
@content2000 Agreed. Screen size limits amt of content per step; how many steps/screens a big consideration. Links prob more impt #tcchat |
|
5:13 pm
|
content2000:
|
@2moroDocs Reusability comes into play. Write critical summary topics as part of main website, then reuse those topics in mobile. #tcchat |
|
5:13 pm
|
2moroDocs:
|
@content2000 If you see any good examples of apps out there with that, cld you post them for us? Think ex very helpful at this point #tcchat |
|
5:14 pm
|
2moroDocs:
|
@content2000 Grt idea. Content management & single-sourcing principles even more impt #tcchat |
|
5:15 pm
|
2moroDocs:
|
You know, we didn't get to graphics, either. That's a major consideration, I think. Can't use as much. #tcchat |
|
5:16 pm
|
2moroDocs:
|
Think graphics is on the list of the mobileOK reqs at W3C site. #tcchat Could b wrong, though |
|
5:19 pm
|
2moroDocs:
|
Check out that First Aid app if u can. Some screen shots. Good integration of text, video, graphics. Some scrolling 4 proc #tcchat |
|
5:20 pm
|
content2000:
|
@2moroDocs no mobile xmpl, but 1st para here is reused in product help.Similar strategy for mobile? http://bit.ly/axPj5q #tcchat #xml |
|
5:20 pm
|
juliov27612:
|
@2moroDocs We shouldn't have to know; that's my main point. Tell device what content is and let hw do its thing. #tcchat |
|
5:21 pm
|
2moroDocs:
|
The app also has drop-down navigation. #tcchat I don't know how to set that up, but it's something I would like 2 know! #tcchat |
|
5:21 pm
|
content2000:
|
@2moroDocs select graphics could be big help-sometimes that pix is worth 1k words ;-) #tcchat |
|
5:23 pm
|
2moroDocs:
|
@juliov27612 Agreed. I c what ur saying. Think that will req more doc planning & we need 2 b aware of hw limitations 4 diff devices #tcchat |
|
5:24 pm
|
2moroDocs:
|
The #tcchat Daily is out - read this Twitter newspaper on http://bit.ly/cmIR1t (19 contributions today) |
|
5:25 pm
|
rjacquez:
|
EPUB is a gd start -->> RT @2moroDocs: @juliov27612 How do we keep up with all that? W/ devices chging all the time, how do we know? #tcchat |
|
5:26 pm
|
2moroDocs:
|
@content2000 Thanks for the link! #tcchat |
|
5:26 pm
|
2moroDocs:
|
@content2000 Offhand, I would say yes. Best to reuse content as much as possible. #tcchat |
|
5:27 pm
|
2moroDocs:
|
@content2000 Agreed. Just can't have bigger graphics, either. Less text, smaller graphics. #tcchat |
|
5:29 pm
|
2moroDocs:
|
@rjacquez Thx. Might you have a link for that? #tcchat |
|
5:30 pm
|
2moroDocs:
|
@rjacquez This, perhaps? http://www.idpf.org/ #tcchat |
|
5:32 pm
|
juliov27612:
|
@rjacquez I agree, RJ. EPUB is a good start. Enrichen the HTML embedded and have devices work with that. #tcchat |
|
5:36 pm
|
2moroDocs:
|
@rjacquez Good to know it's XML. Grt! Would it reflow to make a longer pg & req more scrolling? Reflow due to hw? #tcchat |
|
5:38 pm
|
2moroDocs:
|
If you haven't already guessed, EPUB new to me today. Will def look at it. So I'm prob asking basic ques :) #tcchat |
|
5:39 pm
|
2moroDocs:
|
Darn it! How did I miss this one? Have 2 be out there reading more, I guess. #tcchat |
|
5:43 pm
|
2moroDocs:
|
@rjacquez @juliov27612 Well, Julio, perhaps that would def address your comments #tcchat Good to know! |
|
5:46 pm
|
2moroDocs:
|
I saw something else new 4 me this wk. Augmented reality. @knowledgebishop mentioned the other day. Also, mtg in Sea next wk, I thk. #tcchat |
|
5:47 pm
|
2moroDocs:
|
augmented reality link coming... #tcchat |
|
5:48 pm
|
2moroDocs:
|
Augmented Reality: Pure Hype or Next Big Thing in Mobile? http://bit.ly/5cM0p7 . #tcchat |
|
5:52 pm
|
2moroDocs:
|
I absolutely HATE getting behind on technology. I have a lot of reading to do. Thanks everyone for the links & info! #tcchat |
|
5:53 pm
|
2moroDocs:
|
Another hour elapsed. I have 2 jump off now. This has been a great #tcchat today. Thx to all 4 attending, participating, & viewing! |
|
5:54 pm
|
2moroDocs:
|
In case u didn't see it, today's #tcchat paper published. Links posted yest/earlier are in there. 2moro's will have more & items from S2. |
|
5:58 pm
|
TC_Chat:
|
RT @2morodocs: The #tcchat Daily is out - http://bit.ly/cmIR1t (19 contributions today) #techcomm Has links 4 mobile discussion 2day |
|
6:00 pm
|
TC_Chat:
|
Thx to all that joined & followed #tcchat today. Went for 2 hours! Good points raised, more links. S2 at 7pm PDT #techcomm |
|
6:01 pm
|
2moroDocs:
|
Thx to all that joined & followed #tcchat today. Went for 2 hours! Good points raised, more links. S2 at 7pm PDT |
|
6:14 pm
|
TC_Chat:
|
Transcripts from S1 of #tcchat & yest: Mobile Content Dev. http://bit.ly/bTWO3t #techcomm |
|
6:14 pm
|
2moroDocs:
|
Transcripts from S1 of #tcchat & yest: Mobile Content Dev. http://bit.ly/bTWO3t |
|
6:28 pm
|
DigitalHarbor:
|
@2moroDocs Sorry I missed #tcchat today, transcript looks interesting. |
|
6:32 pm
|
juliebhunt:
|
RT @TC_Chat: Transcripts from S1 of #tcchat & yest: Mobile Content Dev. http://bit.ly/bTWO3t #techcomm |
|
6:33 pm
|
juliebhunt:
|
RT @TC_Chat: Thx to all that joined & followed #tcchat today. Went for 2 hours! Good points raised, more links. S2 at 7pm PDT #techcomm |
|
6:41 pm
|
lrmeyer747:
|
Thanks RT @tc_chat: Transcripts from S1 of #tcchat & yest: Mobile Content Dev. http://bit.ly/bTWO3t #techcomm |
|
7:35 pm
|
juliov27612:
|
@2moroDocs One of my issues with epub is that you still have to prepare for specific platforms. HW should be smarter. #tcchat |
|
11:39 pm
|
dainadunlop:
|
@2moroDocs Sorry I missed #tcchat today. I'll have to miss it tonight as well :( |
| |
|
October 29, 2010
|
|
1:00 am
|
KnowledgeBishop:
|
#Techcomm take note: In exactly one hour, #TCchat session 2 kicks off with more excellent dialog about mobile content! |
|
1:07 am
|
mojoneill:
|
@gdevore @2moroDocs @PattyBlount2 awesome comments during s1! Sorry I had to duck out early! Thanks! #tcchat |
|
1:14 am
|
brandleadership:
|
RT @KnowledgeBishop: #Techcomm take note: In exactly one hour, #TCchat session 2 kicks off with more excellent dialog about mobile content! |
|
1:44 am
|
2moroDocs:
|
@dainadunlop We'll miss you! Can ck transcripts later. Some gd info earlier. #tcchat |
|
1:45 am
|
TC_Chat:
|
15 mins to S2 of today's #tcchat: Mobile Content Dev #techcomm |
|
1:46 am
|
2moroDocs:
|
15 mins to S2 of today's #tcchat: Mobile Content Dev |
|
1:46 am
|
2moroDocs:
|
Yes! Thx! RT @mojoneill: @gdevore @2moroDocs @PattyBlount2 awesome comments during s1! Sorry I had to duck out early! Thanks! #tcchat |
|
1:51 am
|
KnowledgeBishop:
|
RT @TC_Chat: 15 mins to S2 of today's #tcchat: Mobile Content Dev #techcomm |
|
1:56 am
|
2moroDocs:
|
Thank goodness for transcripts. Missed some tweets in S1 as they zipped by. #tcchat |
|
1:59 am
|
2moroDocs:
|
A precursor: today's song of the chat courtesy of @mojoneill http://youtu.be/V92OBNsQgxU Ride of the Valkyries. - Fire it up - #tcchat |
|
2:00 am
|
2moroDocs:
|
Welcome to S2 of today?s #tcchat! Topic: Mobile Content Development #tcchat |
|
2:00 am
|
2moroDocs:
|
Got my music going... Sounds good to me #tcchat |
|
2:01 am
|
2moroDocs:
|
Reminders: please don?t use #techcomm tag. It will overwhelm it. Add #tcchat to your tweets. Thx! Also, no proprietary info! |
|
2:01 am
|
2moroDocs:
|
Main topics: writing style. Mobile minimalism (mm); usability, hardware, system reqs, #tcchat |
|
2:02 am
|
2moroDocs:
|
So how about a roll call? #tcchat |
|
2:03 am
|
mojoneill:
|
Boohyeah... In from the growing megalopolis of Iowa City, IA...but sleepy. ;P
#tcchat |
|
2:03 am
|
2moroDocs:
|
Noted this earlier; will toss out again. First: mobile use increasing significantly. 2-yr growth of over 2,000 % #tcchat Can't ignore it - |
|
2:04 am
|
2moroDocs:
|
2010 study of mobile Web trends shows continued explosion of mobile-friendly content #tcchat . http://bit.ly/aGDq6d |
|
2:04 am
|
2moroDocs:
|
@mojoneill Hi there again! Twice in one day. Appreciate it. Love your song choice #tcchat |
|
2:05 am
|
sausagebot:
|
RT @2moroDocs: 2010 study of mobile Web trends shows continued explosion of mobile-friendly sausage #tcchat . http://bit.ly/aGDq6d |
|
2:05 am
|
2moroDocs:
|
Q1: Screen size is small. MM: how much do you cut? What is max no of screens in a series to go through? #tcchat |
|
2:06 am
|
mojoneill:
|
@2moroDocs Yeah. Wagner is cracking me up (how often do you get the opportunity to say that?!?!).
#tcchat |
|
2:06 am
|
kirstyt:
|
Hi there #tcchat! |
|
2:06 am
|
2moroDocs:
|
A1: Earlier, @mojoneill, think you said 7 +/- 2 #tcchat |
|
2:07 am
|
2moroDocs:
|
You know, how about if we discuss video? Didn't have time for that earlier #tcchat |
|
2:07 am
|
kirstyt:
|
#tcchat A1: Try to keep it really simple. Put hints in UI where possible, rather than sep ua/doco. |
|
2:08 am
|
2moroDocs:
|
Q2: How do you add or use video on mobile? #tcchat |
|
2:08 am
|
2moroDocs:
|
@kirstyt Hi there! Happy Friday! #tcchat |
|
2:08 am
|
mojoneill:
|
Well, the 7 +/- 2 was more of a joke based on the theory of the ideal number of concepts, etc...
#tcchat |
|
2:09 am
|
kirstyt:
|
A2: We haven't done that yet (or actually UA on mobile yet). #tcchat |
|
2:09 am
|
mojoneill:
|
Hi Kirstyt!
#tcchat |
|
2:11 am
|
2moroDocs:
|
A2: I've seen just some. One is in an app I mentioned earlier that I downloaded. Video is small in it, but works #tcchat |
|
2:11 am
|
2moroDocs:
|
Other video items perhaps. Larger full-screen that chg when you chg phone from portrait to land #tcchat |
|
2:11 am
|
mojoneill:
|
The problem I have with mobile content (and it is MY problem) is that I consume so little of it.
#tcchat |
|
2:12 am
|
2moroDocs:
|
When might one go w/a smaller mini-video vs one that takes up whole screen? #tcchat |
|
2:12 am
|
mojoneill:
|
It's grown 2billion percent yoy, but is most of that twitter, sms, and social media + kindle books?
#tcchat |
|
2:14 am
|
mojoneill:
|
(obviously exposing my inner Luddite) ;P
#tcchat |
|
2:14 am
|
2moroDocs:
|
@mojoneill Same here. But if I'm out on the road or something, I use it more. #tcchat |
|
2:15 am
|
2moroDocs:
|
@mojoneill Might depend on an app, too. the First Aid one I downloaded nice 2 have on my phone. Perhaps other info like that avail #tcchat |
|
2:17 am
|
2moroDocs:
|
The other item we barely touched on was graphics. #tcchat |
|
2:18 am
|
2moroDocs:
|
Q3: How do you use graphics in mobile docs/content? #tcchat |
|
2:19 am
|
2moroDocs:
|
Maybe you would use a lg image for main docs & thumbnail for mobile. ??? #tcchat |
|
2:19 am
|
2moroDocs:
|
that might be handy from single-sourcing standpoint. Could use thumbnails in multiple places, no doubt. #tcchat |
|
2:19 am
|
kirstyt:
|
A3: We avoid graphics as much as possible. Might put them in printed doc for mobile products, but not in mobile doco. #tcchat |
|
2:20 am
|
mojoneill:
|
@kirstyt do you produce content for mobile? #tcchat |
|
2:21 am
|
2moroDocs:
|
@kirstyt Is that for maintenance reasons, or just focusing on text instead? #tcchat Something else? |
|
2:22 am
|
kirstyt:
|
Could also just highlight the portion of screen/app that's relevant, not a full s/shot. #tcchat |
|
2:22 am
|
kirstyt:
|
@2moroDocs Cost of maintenance and cost of internationalisation. #tcchat |
|
2:23 am
|
2moroDocs:
|
Sometimes it is nice to have a graphic, but generally they're fairly larger in docs. Mobile, only small?. Unless zoom planned? #tcchat |
|
2:25 am
|
2moroDocs:
|
@kirstyt Gd points. So I"m guessing that perhaps it would have to really be justified to include a graphic sometimes. #tcchat |
|
2:26 am
|
2moroDocs:
|
Something else w/graphics. Callouts not likely, I would think. mobileOK recommends against image maps, too #tcchat |
|
2:27 am
|
kirstyt:
|
@2moroDocs Exactly. The user is already on that screen, why replicate it? Unless it helps with providing some instruction. #tcchat |
|
2:27 am
|
2moroDocs:
|
Let's jump to usability. I was thinking earlier... #tcchat |
|
2:27 am
|
ms_marques:
|
@kirstyt Those costs are true even for non-mobile doc #tcchat |
|
2:28 am
|
2moroDocs:
|
Usability, of course, always very impt 4 docs. So I wonder... #tcchat |
|
2:28 am
|
2moroDocs:
|
Q4: is usability even more impt for mobile than it is for traditional docs? #tcchat |
|
2:29 am
|
Kristil:
|
@kirstyt We thought that at my last place, but then ppl asked for more images. Now I'm experimenting with what reduces reading. #tcchat |
|
2:30 am
|
Kristil:
|
@2moreoDocs @kirstyt Hi, by the way. :) #tcchat |
|
2:30 am
|
2moroDocs:
|
@kristil Hi! Thx for dropping by - #tcchat |
|
2:30 am
|
kirstyt:
|
@mojoneill *For*, but not currently on. Devs focussing on geting code working, without going into UA on mobile. #tcchat |
|
2:31 am
|
2moroDocs:
|
@ms_marques Thx for joining in - #tcchat |
|
2:32 am
|
mojoneill:
|
@2moroDocs interesting idea. but I'd think usability is not platform specific... meaning, unusable content on either platform sucks #tcchat |
|
2:32 am
|
mojoneill:
|
@Kristil Hiya!
#tcchat |
|
2:32 am
|
mojoneill:
|
usability should be a universal goal
#tcchat |
|
2:33 am
|
kirstyt:
|
@ms_marques And it's our non-mobile docs that caused that stance. We have 2 products, each with ++2000 screens. #tcchat |
|
2:34 am
|
kirstyt:
|
A4: #tcchat Yes. Our mobile users can be less computer literate than desktop users. Will vary, naturally, but they should be simple to use. |
|
2:35 am
|
2moroDocs:
|
With smaller screens, think that point size, no of screens to scroll through, & color may be more impt. #tcchat |
|
2:35 am
|
2moroDocs:
|
@mojoneill So true! #tcchat |
|
2:35 am
|
kirstyt:
|
@Kristil It is tricky. We have some products that are highly customised on-site, so a s/shot will not reflect what the user sees #tcchat |
|
2:36 am
|
2moroDocs:
|
@kirstyt That's a lot of screens, especially if they tend to change periodically - #tcchat |
|
2:37 am
|
mojoneill:
|
@kirstyt Do you document screens, or processes (or both or neither)? #tcchat |
|
2:37 am
|
Kristil:
|
@kirstyt Good point. I'm trying to work in more conceptual diagrams, too, but I'm a bit intimidated. Need more practice, I guess. #tcchat |
|
2:38 am
|
2moroDocs:
|
@kirstyt Can see why u don't want to use them much. Accuracy goes out the window. #tcchat |
|
2:39 am
|
kirstyt:
|
@mojoneill Both. Doc all fields all screens, then processes & activities using those screens. User can go thru 3-4 screens/activity #tcchat |
|
2:39 am
|
2moroDocs:
|
What abt graphics that aren't screen shots? Just some picture or something you make to show a concept? #tcchat |
|
2:39 am
|
Kristil:
|
@2moroDocs I'm trying to coordinate callouts with text in a way that shots could still be helpful if they don't get translated. #tcchat |
|
2:40 am
|
kirstyt:
|
We still try to use process flow graphics, and would translate them when needed. #tcchat |
|
2:44 am
|
2moroDocs:
|
So a big consideration continues to be translations. That wld certainly affect mobile output. Variable text length, too, sometimes? #tcchat |
|
2:45 am
|
Kristil:
|
I'm curious what kinds of help people are making for mobile. Tooltips? Text in the UI? Or full on help topics? I haven't done mobile.#tcchat |
|
2:46 am
|
2moroDocs:
|
This is something I'd like to look into: is anyone using text abbreviations in mobile docs yet? #tcchat |
|
2:47 am
|
mojoneill:
|
@Kristil that's where I keep getting stumped too . :) #tcchat |
|
2:48 am
|
2moroDocs:
|
@kristil I've seen WordPress sites turned into mobile. Also, that first aid app I mentioned is actually an online manual. Slick! #tcchat |
|
2:49 am
|
2moroDocs:
|
@gdevore had some examples earlier. He might be a good person to ask. #tcchat |
|
2:50 am
|
mojoneill:
|
@2moroDocs does it have the requisite illustration of a compound fracture?
#tcchat |
|
2:51 am
|
2moroDocs:
|
@kristil Think it would depend in part on audience, how docs/product used. #tcchat |
|
2:52 am
|
2moroDocs:
|
@kristil If ur docs are on the web, and websites can be made mobile-ready, then I think we can assume docs may b on mobile. #tcchat |
|
2:54 am
|
2moroDocs:
|
@mojoneill Probably! Has CPR info, for sure. :-) #tcchat |
|
2:54 am
|
Kristil:
|
@2moroDocs That's an interesting spin: UA as apps. Docs I've worked on wld need serious tweaking to fly that way. #tcchat #blownmind |
|
2:56 am
|
mojoneill:
|
to me, the exciting thing about mobile is in the push. content pushed to mobile (like sms) has a crazy-high read rate compared w/eml #tcchat |
|
2:56 am
|
2moroDocs:
|
@kristil Agree! Take a look at the WP plugin that can chg a blog into an app #tcchat I'll go find the link. Very cool |
|
2:58 am
|
Kristil:
|
@2moroDocs By tweaking, I mean making them worth downloading separately.Is anyone documenting a mobile app that really requires that?#tcchat |
|
3:00 am
|
2moroDocs:
|
@kristil Only ex I can think of at the moment is my phone help. Can open it in a window & still use the phone & its many functions. #tcchat |
|
3:01 am
|
mojoneill:
|
mobile content: finding out you can is not the same as knowing that you should.
#tcchat |
|
3:02 am
|
2moroDocs:
|
I'm not sure it's always about documenting a mobile app. Perhaps accessing app/info via mobile; need docs to accompany ??? #tcchat |
|
3:02 am
|
Kristil:
|
@mojoneill Hmm, maybe mobile alerts when the product requires input or to monitor things, like a bank account alert. #tcchat |
|
3:04 am
|
2moroDocs:
|
@kristil Good ex. May need docs to provide info re types of alerts #tcchat |
|
3:05 am
|
Kristil:
|
Wonder if the doubts I have about making help topics for mobile could be said of any help topics. #tcchat |
|
3:05 am
|
2moroDocs:
|
I could see safety manuals having a huge requirement/use for this. Many regulatory requirements... #tcchat |
|
3:06 am
|
Kristil:
|
Like I would Google, ask someone, abandon the app, or throw the phone before I would use a help topic on mobile. #tcchat |
|
3:06 am
|
2moroDocs:
|
For ex, if there's an accident/incident, coordinators may need access to safety info online. May b critical. #tcchat |
|
3:07 am
|
mojoneill:
|
@2moroDocs How about driving instructions on mobile device? ;P
#tcchat |
|
3:07 am
|
2moroDocs:
|
@kristil Maybe their brevity on mobile would help that, though. #tcchat |
|
3:08 am
|
mojoneill:
|
@2moroDocs I think those examples are spot on. But IMO it's no longer a content/app dichotomy. they are apps that provide content. #tcchat |
|
3:09 am
|
2moroDocs:
|
@mojoneill Hey - let's get some voice in there. GPS directions? ;P #tcchat |
|
3:11 am
|
2moroDocs:
|
@mojoneill Yep. A good way to market them, too. Not help - no need to throw the phone away @kristil! An app. Make docs an app #tcchat |
|
3:12 am
|
Kristil:
|
@mojoneill @2moroDocs Yes, content apps. Head spins with ideas. But then I have to ask devs to build it & marketing to deliver it. #tcchat |
|
3:12 am
|
mojoneill:
|
mobile content is so last month. the question of the day is how to utilize new 3d displays... :) #tcchat |
|
3:13 am
|
Kristil:
|
@2moroDocs But I think that's likely overkill for a mobile app. I just have to convince devs to let me sneak some UA into UI. #tcchat |
|
3:14 am
|
2moroDocs:
|
@kristil Maybe not. That WP plugin looks relatively painless. Have 2 try it though. Maybe there's something out there. Need 2 look #tcchat |
|
3:15 am
|
2moroDocs:
|
@mojoneill You know what I would love to see? A hologram screen pop up on my phone and have docs display like a drive-in movie #tcchat |
|
3:16 am
|
Kristil:
|
@2moroDocs Ok, @ me when you find that link. Have to run, so nice talking to you @2moroDocs @kirstyt @mojoneill #tcchat |
|
3:17 am
|
mojoneill:
|
I think its time for me to turn in too. Getting goofy.
#tcchat |
|
3:18 am
|
2moroDocs:
|
Sheesh. Didn't even notice that it's now ~ 8:15 here. We're over time! I can stay around a bit... #tcchat |
|
3:18 am
|
mojoneill:
|
thanks for hosting Julie, and thanks to everyone else for the good discussion. #tcchat |
|
3:18 am
|
2moroDocs:
|
You really have me thinking. I'm now wanting to go look at apps more & app dev 2 c what possibilities there are 4 making doc apps #tcchat |
|
3:19 am
|
2moroDocs:
|
I had played around in VisualStudio a bit to try & make a doc app. I don't see why we *can't* do that. #tcchat |
|
3:20 am
|
2moroDocs:
|
Thanks everyone! Appreciate your staying up late to join in! #tcchat |
|
3:21 am
|
2moroDocs:
|
@kristil Will go find it now. Lost in a sea of tweets today. I know it's there, though. #tcchat |
|
3:26 am
|
Anzac:
|
RT @Kristil: Like I would Google, ask someone, abandon the app, or throw the phone before I would use a help topic on mobile. #tcchat |
|
3:26 am
|
2moroDocs:
|
@kirstyt Here's the link to the WP plugin that makes blog work like an app http://bit.ly/VoU5 #tcchat |
|
3:26 am
|
2moroDocs:
|
Night all! #tcchat |
|
3:32 am
|
2moroDocs:
|
@mojoneill @kirstyt @kristil @ms_marques Thanks for the chat convos tonight! #tcchat |
|
4:15 am
|
kirstyt:
|
@2moroDocs Thanks for the #tcchat! Sorry I had to bail, it was getting around 1pm, and my tummy was yelling at me. :) |
|
4:47 am
|
ermphd:
|
Found this by Gooogling "UI +tablet" http://youtu.be/sM91fVgkkOg <like to see more actions> #TCchat |
|
4:56 am
|
SingleSourcing:
|
Great Link ! RT @2moroDocs: @kirstyt Here's the link to the WP plugin that makes blog work like an app http://bit.ly/VoU5 #tcchat |
|
6:19 am
|
2moroDocs:
|
@kirstyt No worries! Thanks for joining in. Have a great weekend - #tcchat |
|
6:20 am
|
2moroDocs:
|
@ermphd thanks for this link! #tcchat |
|
6:22 am
|
2moroDocs:
|
@juliov27612 Thanks, Julio. I need to learn more about it. Agree - hw should be smarter. #tcchat |
|
1:53 pm
|
ermphd:
|
Interesting post on "rise of tablets in eLearning" http://bit.ly/aXTABC New market channel is upon us #Techcomm #TCchat |
|
2:00 pm
|
Kevin_Siegel:
|
RT @ermphd: Interesting post on "rise of tablets in eLearning" http://bit.ly/aXTABC New market channel is upon us #Techcomm #TCchat |
|
2:19 pm
|
Interactyx:
|
RT @ermphd: Interesting post on "rise of tablets in eLearning" http://bit.ly/aXTABC New market channel is upon us #Techcomm #TCchat |
|
3:00 pm
|
richsmolen:
|
RT @Interactyx: RT @ermphd: Interesting post on "rise of tablets in eLearning" http://bit.ly/aXTABC New market channel is upon us #Techcomm #TCchat |
|
4:31 pm
|
PattyBlount2:
|
@juliov27612 @joybwriter @mojoneill @KnowledgeBishop Thanks for the #tcchat love, you guys! |
|
4:33 pm
|
juliov27612:
|
@PattyBlount2 You're quite welcome for the #tcchat love. |
