First day feedback
Tuesday, August 28, 2012 at 9:50AM One of the things I’ll be trying to figure out here is whether the notion of blog comments-based feedback is enough. Perhaps not. But … let’s see how that goes. :)
First, and most obviously, thanks to everyone that’s commented here, written me email, or pinged me on Twitter. The feedback has been overwhelmingly positive, which I appreciate. I should respond to a few of the more common types of comments I’ve received.
Tip jar/donations. At least a few people have mentioned the notion of a virtual tip jar or whatever. Don’t worry about that: I’ll be using parts of this book as inspiration for feature focus articles on the SuperSite going forward—and yes, I mean “inspiration,” not “cut and paste”—and so on, where there are ads and a revenue stream. I’m doing this book as an experiment of sorts and want to see how it goes. And I really care about Windows Phone, so it’s something I want to fully explore. As with the original Windows Phone Secrets book, the goal was largely about forcing myself to learn something inside and out, not to make money. As with that book, I expect to be successful at both here as well. :)
Other topics. A few people have asked about other topics such as Microsoft Office 2013. I picked Windows Phone for a number of reasons, but aside from sheer enthusiasm/advocacy, it’s fair to say that Windows Phone is an approachable, finite topic that can be effectively covered in a far smaller space than something big and complicated like Office, or other topics I considered, like “Learn Windows 8 Programming with Paul” or whatever. There will be other projects in the future, but let’s worry about one book at a time.
Rafael. I of course discussed this book with Rafael before I went public with it. Rafael and I speak every day, often for hours, and while I did give him the offer of a lifetime—something like “you can have 50 percent of the $0 I’ll make, 75 percent of the $0, whatever, it’s you’re call—he won’t be formally writing the book with me. That said, I will be discussing this with him regularly, probably almost daily, and I bet you see a lot of him here. (The “nutter” thing is an inside joke. Please bear with us.)
Publishing end-points. I’ve gotten a few questions about the formats this can/will be published in, and my goal is for this to happen in as many formats as possible (as well as in native apps, etc.) So if you need/want ePub, or whatever, I don’t see any reason why that won’t be the case. The trick, here, of course, is that the book will start happening at some point, and I suspect the first many number of drops will be whatever format only, like PDF or Word format or similar. But as it gets closer to something real, I’ll need to start thinking about those other formats. I may need help with conversion, etc. But that’s for the future.
Site template. As many of you have noticed, I’m using Squarespace for this blog, and have been waiting for an excuse to try it out. I have done less than nothing to modify the look and feel of the site, but will do so in the near future. I guess that’s not a huge priority, but it will happen. I want it to look nice, and have some sort of non-infringing Windows Phone “style.”
Other ways of publishing. A few noted other forms of book publishing, like MEAP (Manning Early Access Program) and what Ed Bott’s doing with his Windows 8 title. I’m not familiar with either, sorry, but if I’m understanding this properly, and perhaps using Charles Petzold’s new Programming Windows book as a guide, those publishing styles are a bit more like traditional publishing than I’d like. I don’t want to write 5 or 8 chapters or whatever and then present it to the world. I want to write parts and then present it much more frequently—perhaps daily in many cases—so I can get feedback immediately. So while I will be the one writing the book, per se, it will be heavily influenced by feedback and, hopefully, made into something that is more complete/concise/correct … or just “better.” I can already write a book, I’ve written something like 25 of them. I don’t want to do that this time. And if this works out, this is the future.
Compared to wiki/help file/etc. Many have compared the plan here to a crowd-sourced wiki, help page, or similar, and that’s probably fair. One thing I’ll bring to this, however, is a book structure. There will be a “cover,” front matter with introduction, “chapters,” and so on. It will be structured something like a book. I think. We’ll see. :) That said, there are issues around referencing other parts of the book. For example, in a book like Windows 8 Secrets, we will have a line like, “we discuss this feature more in Chapter xx” or whatever. While writing what I think of as a book-book, these passages are often highlighted in yellow so we remember to go back and make sure they’re always correct. There are absolutely mechanical parts of this process I’ve never had to deal with before. But the structure of this book—by “chapter,” by topic, by scenario, or however it comes out—will help drive this. Ideally, the book will be structured in such a way that one could read it front to back or just cherry pick topics and not worry about referencing other parts too much.
Hyperlinks. In a similar vein, a true, electronic-only title could have lots of hyperlinks in it for moving around in the book. I suspect this will be part of it, but we’ll need to figure out how to handle those links in the “print” and eBook versions. Maybe just traditional references.
Specific content ideas. A few people have made suggestions about the types of things that could be in the book. One thing I wanted to include in Windows Phone Secrets but had to cut because it was just too early in the product’s lifetime and the information/capabilities just weren’t there yet was the notion of a “how to transition to Windows Phone from other platforms” chapter. This should of course be a part of this book. But I’ll begin the discussion about how I view the content/topic/chapter list soon. Obviously, this one has sort of been preoccupying me lately.
Research. One thing that you may find interesting is how I cull information. One of the next posts will be a deconstruction of the Windows Phone Summit event from June which is still, I believe, Microsoft’s only major public communication about Windows Phone 8. I’ll watch the video, take notes, and show how I’d break what’s in there down into specific parts of the book. I’ll do similar breakdowns for other sources of information I already have, too, and in the future will do so from meeting notes and future events.
OK, hopefully I didn’t miss anything. I’ll be commenting inline in the comments section normally, of course, but I just wanted to kick this off in way that makes sense for where we are at the beginning of this.
I think the next thing will be a topic breakdown. One thing I’ve learned from doing this for so long is that the first version is always a mess, and will always change.
Reader Comments (16)
Here's another vote for the “how to transition to Windows Phone from other platforms” chapter. Inertia is the killer of innovation and change, and if like me, you have five years invested in the iPhone and iOS applications, it is critical that we have a plan and path to transition. It's much worse than just "muscle memory" when you try to match up comparable software to your work experience over such a long time.
I absolutely love your concept for this new book. I am looking forward to reading and hopefully contribute in a way that you find valuable.
On the topic of published formats. Have you considered creating a responsive web site as the book? You could still provide downloadable eBook formats as well but this would allow web users from any device to read and navigate the book with ease.
Just a thought.
Hi Paul!
I'm really excited about this process, both for the topic and to see how you adapt the writing process to more modern times and concepts. I'm also excited about being able to essentially "read" the book in real-time as you write it, and offer feedback. As a Windows Phone enthusiast myself, I've learned a lot from reading your articles and listening to you on Windows Weekly, etc...
Looking forward to it!
Paul
What i look forward to is the management side of WinPhone 8 and your chapter on that. The one thing i find WinPhone 7.5 lacking in is the Enterprise management posibilities. We just fininished a roll out of all Lumia 800's for alle employees (450) and did away 97% of our traditional phones and use Lync for presence and collaboration. We are eagerly awaiting the Symantec Athena plugin for sccm 2012 and hope de feature set will be broader than current MDM solutions. All employees love the Lumia btw and the reactions on WinPhone are extremely positive. Even the former Iphone users aren't looking bach <grin>. So really looking forward to your ideas on that aspect in the book
A goal: Always force yourself to think beyond the content. Content is king, but the forum and method of development will determine the content's ultimate quality. This forum and development is guided by people. When the effort is in some ways crowd-sourced, it's imperative to make sure that a community remains vibrant and engaged. A vibrant, invested community will help produce an even better product (though product describes something finite, which I would discourage).
Prioritize the most interactive model you can stand. It will mobilize the enthusiast and casual community. A live community chat/weekly video podcast with updates would be a great place for encouraging interaction - something people can subscribe to/watch live; maybe in the form of a conversation with Rafael or other guests regarding book progress and invite a chatroom's feedback. Read and respond to interesting comments. Maybe even consider a community manager.
This has the chance to become a dominant source of windows phone 8 conversation - craft a high quality, publishable material, but also, create a conversation of learning and guidance for users looking for answers about windows phone 8 and they will come.
The development of online education is a huge interest of mine and this is a great opportunity to do with a new OS something I've only seen realized in a great site like Codeacademy. Beyond WP, I'm pretty sure that we're looking at the future of education.
I am excited to be a continued contributor.
Paul,
I can't speak for Epub, but I know that on the Kindle book that I've published, I had all sorts of links within the text to other parts of the text (chapters, paragraphs, whatever). Surely Epub has a similar capability. Like whatever is used in the TOC.
Concerning 'Publishing end-points':
* How about starting off with a plain old-fashioned RSS feed? This would enable us to keep up with your latest writings - right from a Windows Phone.
* Maybe later: I really like the idea of some sort of an App-reader-something enabling me to read an online version of the book-book?
“how to transition to Windows Phone from other platforms”:
Not sure on significance of this subject. Personally, as a consumer I do not feel a need for this: I just started using my 900 - no problem. But that could of coarse be different for a phone used in an enterprise environment?
"Hyperlinks"?
Personally I'd prefer references at the end of a page/chapter/book. AFAIC links are to easily distracting one from the actual reading context. And i't to be a book-book - not a wiki/website?
(Additionally this would also be better to handle for the print-version :-)
Another subject that comes to mind: The Windows Phone being a connected device, there should be a topic on its implications concerning privacy and security?
(I still have my doubts on installing that cute 'free' app on the same device I use for banking ;-)
Concerning 'Publishing end-points':
* How about starting off with a plain old-fashioned RSS feed? This would enable us to keep up with your latest writings - right from a Windows Phone.
* Maybe later: I really like the idea of some sort of an App-reader-something enabling me to read an online version of the book-book?
“how to transition to Windows Phone from other platforms”:
At this point I'm not sure on the significance of this subject. In an enterprise context I can imagine this being an important issue.
"Hyperlinks"?
Personally I'd prefer references at the end of a page/chapter/book. AFAIC links are to easily distracting one from the actual reading context. And i't to be a book-book - not a wiki/website?
(Additionally this would also be better to handle for the print-version :-)
Hey Theo, there you hit something i liked. I wonder if its a easy way to describe it so you dont fall asleep reading it also :-).
Looking at the "this app needs access to" always make you wonder. The description may look the same on a app in Google Play store, but are the same data collected the same way? Would be nice to have that on print. Right now im just asuming its far from the same personel data being collected.
Anyway, liked the idea. May put WP in better light for people actually wondering/searching (seeing how Google sells phone im not sure this matters to most people) these questions.
Best Regards
Peter Nakazul Wiik
Hi Paul,
this is such a great idea. go for it!!! I can't wait to see how it all pans out. I am so looking forward to doing development on Windows Phone 8. Loving developing a Win RT/Metro/Modern app at the moment.
I think we are on the brink of a new revolution in the way people interact with each other through the internet and Windows Phone 8 will be a big player in that process.
Looking forward to seeing how this pans out.
Pete
after listening to last week's Windows Weekly - a title suggestion "Windows Phone Essentials"
also, topics about transitioning from Windows Phone 7, or details on how well the WP7 apps run on WP8 devices, etc.
Looking forward to this next-generation book (and the new devices!)
I think a useful section (especially for crowdsourcing) would be usage scenarios, whether with native capabilities with the OS or in conjunction with apps. I think it would be interesting to categorize it by topic like "music sharing" or "document editing" and the like. I imagine there are many things that I would discover about the usefulness of WP8 from other's experiences.
Thanks for this site. I currently have an iPhone and are looking to move towards windows phone/Nokia. I live in Australia, would it be possible from time to time talk about topics internationally. I love hearing about features of the north american market, but a lot of those features are not apart of our market.
P.S. hope you enjoy New Zealand, I been there many times. It's a beautiful part of the world.
I'll throw my support behind the idea of a comprehensive walk through of switching from other platforms. It could even involve readers that have direct knowledge of the process being able to contribute their advice or share their experience? That could serve as a roadmap of the necessary steps from say someone who transitioned from Android & can say "be on the look out for or pay close attention to this step in the process." I myself I'm very ready to transition away from Android & try Windows Phone. I'm not interested in Apple as I'm a Windows user & am invested in Microsoft's ecosytem except the phone platform. The main obstacle standing in my way is that I'm locked into Verizon since the rural area I live in is covered by Verizon & ignored by the other wireless carriers. But rumor now says that Verizon & Nokia/Windows are getting ready to finally tie the not? I hope so.
Either way I'll keep a daily eye on this space & look forward to this process. I wish you much success on this unique experiment. With any good fortune I'll be able to join the Windows Phone community of users & can contribute to this as well.
How about OneNote Format
Microsoft Office OneNote as a format. Available free on the Web. Also available on Android, IOS, Mac and Windows Phone.
Great Search on PC and Web.
Each feature or sub-feature could be on a separate Page. Chapters could be in Sections.
Downloads could be by Page, Section, or Notebook.
Easy to reorganize. Easy to annotate.
Downloadable from a public SkyDrive site.