Quote
Hurricane John - 2007-07-09 12:26 PM
Quote
PhotoAngleMemory - 2007-07-08 2:50 PM
In the H/PC community there's a "already been done" feeling I think. Which may be why there's difficulty in getting writers. H/PCs are little past their glory days.
But that's just what I think. May not neccesarily be true, but it seems to me that the lack of involvement is because there's new tiny shiny toys out there that outglory the H/PC.
Don't look now, but PPC's are on their way out......everyones getting one of them swiss army knife type smart phones with those teenie, weenie tiny little screens!
... trying to play Halo 2 and write a doctoral thesis on it, yeah, yeah, same old drill as the PPC users - just that little bit more sadistic.
However, if someone should want to write a review using a SP, I wouldn't begrudge it... assuming the quality was right.
PhotoAngleMemory,
If you want to have a go, I am positive that we can find you something to whet your whistle with. All in all, the worst thing that can happen is for us to say 'no'. If you can stick to some general principles which apply universally, then it isn't too likely to happen.
Review Principles (for everybody)
- You aren't creating a picture book. Graphics are there to enhance what you are saying. I can go and download the trial and see every aspect of the UI myself. I'm only interested in why I should spend the time downloading the trial!
- When I am proofing for publication I delete all the pictures. If I cannot understand what you are referring to
(save for absolutely necessary use of "see the screen shot below"
), it doesn't get published. Your words have to tell me everything about the program.
- No slang and preferably no coloquial expressions in the main review body. Your intended audience is international, not a corner of the US North West. Making a great joke about Martha Stewart in your reivew may be well and good, however there is a good chance that 5.7 billion people in this world have no idea who Martha Stewart is: If you're going to be cute, please elaborate as is necessary.
- Use of "I". Please try and minimise it.
- Spelling, punctuation and grammar. Aside from UK/US/Int English differences - we will publish in your native English.
- The sure fire way for me to a
) stop reading a review and b
) refuse to publish it is if you are reciting the users manual to me. I can read, we can all read or we wouldn't be here. If I wanted to read the features list, I'd go to the manufacturer and read the features list. As a reviewer you are trying to tell me why I might be interested in the program
(or why I shouldn't touch it with a 100m pole
).
If you can tell me that, great. If you can tell me something no other reviewer has, excellent. If you can tell me something the manufacturer didn't know - Fan-tas-tic.
- Who are you writing for? Usually a good idea to spell that out somewhere near the beginning. If I'm a 2.11 reader and the app only works on CE 4.2...
- Don't be afraid of being critical when and where it is fair and necessary to do so. We usually give developers a lead time on the review before publishing. There have been frequent instances in the past where warranted criticism in a review has led directly to changes in the application. A quick edit to the document to add that they responded and fixed some of the comments always looks good for the reviewer and the manufacturer.
- "http://". I was once at a seminar, many, many years ago being told by an "expert" just how wonderful hyperlinks are. Being told how great it is that the net is a non-linear system and why every website should make as much use of hyperlinks as possible so that all information can be intertwined with all other infomraiton. That's very nice if you're wikipedia.
If I see "http://" in a review, what you are saying to me the reader is "here, please leave this website, please leave half way through my review; you don't need to finish reading it".
Guess what. As a website owner I do not want readers to leave the website, and I'd much rather that they read all of your thoughts, ideas and absorb your hard work!
- If you can, try and comment on the manufacturers support procedure/efficiency as we do score based upon support. For John Ottini a particular bug here is the registration system for payware. For Clint it's response time on email. I usually go for the built-in help.
- Conclude. You can freely use "I" here.