Archive | February 22, 2010
Tweets
- RT @alansmlxl: The What's Next for Business: ht.ly/bjB9R #futurebusiness #designthinking fb.me/14xLQkIB5 2 hours ago
- RT @aricochet: Do you really wan to live forever? The case for non-existence bit.ly/LfOBmP 2 hours ago
- RT @mymodernmet: Grant Snider's Great Comics on Art and Inspiration su.pr/8mMw8D - awesome 10 hours ago
- Smashbuger at Stonecrest. And yes, those are sweet potato fries twitpic.com/9rqs9b 12 hours ago
- RT @johndyer: What a beautiful day to sit outside and just look at stuff on your phone for a while. -- everyone at Starbucks today. 14 hours ago
- RT @theredheadsaid: Adorable - 24 tai chi poses by a mouse quezzie.deviantart.com/art/24-Posture… 15 hours ago
- [#NP @lastfm] R-Swift – Transformed bit.ly/JFnK6o 15 hours ago
Post Calendar
Comments/Referrals
- Curt on Thoughts for a Mobile Device’s Contextual UI
- Carnival of the Mobilists #271 at MobiThinking « Blog.AntoineRJWright on Antiquated Features of Modern Mobile Phones
- Polly on Time & Value as the Only Mobile/Tech Indicator that Counts
- Time & Value as the Only Mobile/Tech Indicator that Counts « Blog.AntoineRJWright on Time, The Reason Why Mobile Fails
- Bronwen Katsaros on Time, The Reason Why Mobile Fails
Categories
- Bicycling (45)
- Carnival of the Mobilists (47)
- Commentary (269)
- Mobile (447)
- Mobile Ministry Magazine (MMM) (33)
- Poetry (28)
- Site (10)
- The Librarian and the Yellow Canoe (1)
Other Contributions
- All Books Project
- Brighthand
- Ideas Project
- iPad Artwork Gallery
- iPad Creative
- Mobile Ministry Magazine
- Mobile RnR
- Notes.AntoineRJWright – Bible/Sermon Notes
- Palm Addict
- Sketchnote Gallery
- Smart Mobs
- TAT Future of Screens Video
- [Interview] BBC Outriders Podcast
- [Interview] No Ties Allowed Podcast
- [Tablet UI Blog] WordPy and Linear UIs
- [Video Presentation] Visual Story Network
- [VoIP Survivor] The Mobile Address Book

Are Document Files (Formats and Containers) Necessary
Today, I’ve had two content issues which required the passing of one file to another person (via email, ew). In both cases, I wonder if those files were even needed, since both sets of content could be displayed in-browser versus needing a dedicated application.
The first instance was of an Excel document. Now, there are two of us working on this document and both need the main columns, the information would be brought together later. Thing is, with SharePoint, you cannot collab on a document like that you have to wait until the other person checks it back in and then you can append your changes. For this type of analytic work, its tedious.
What could work here is to use a SharePoint list, put the columns in there to match the spreadsheet, add choice and text fields for input areas, and then we could both work on this at the same time. And then for the 3rd party that needs to see this, they can simply go to the list (in a Read-Only account) or get the results by using the Export to Access or Excel function. Never needing to open Excel for this at all really – add some type of reporting layer and you’d really never need it.
The second one has to do with a site redesign. Now, I’ve already got the document in an online repository, but not everyone would have access to it. I could open it, but then I lose the free-form ability to create the wireframes as I had intended. This is initial thinking and very high-level, so doing detailed work doesn’t apply, and neither should a dedicated app. Problem is, I need to take it out of the dedicated app’s format, and put it into something that is more SVG *and* slide friendly that works in a browser.
This would be another collaborative event, but the kind that – again – working in the browser would come in handy for. In addition, I’m on mobile just often enough that to use the browser to display this would make sense (in SVG terms) since it would scale appropriately.
I don’t know if too many people are ready for this, but I know that I am. I’d rather have to just think about the content, instead of debating to think if they have the right plug-in or version of the application. If I know that the browser(s) are up to snuff – and most modern ones are – then collaborating like this should be where we go with computing. Not, taking yet another error message and building an application for yet another (antiquated?) format.
Worst of all, enterprises could really use this kind of thinking, but don’t even look to exploit all that beautiful hardware (servers, laptops, and people) that could make this easy.