Cellphone platform, recommendation 2

Wizzy, could you write something "with bite" for this? I don't even own a cellphone, and I feel like I'm the last person who can write that recommendation. (though I did add a couple of links & refs) Could you have a go? I will email you the log of last Thursday's discussion, which covered this. I'll also try to write a short summary, though of course I'm running out of time!

Do you think I'm waffling too much in nos. 3 & 4? I'm trying to keep the points down to 1-2 sentences, but some are complex issues. If we oversimplify, they may think we haven't thought about the issues in depth; if we are too long, we run the risk of them losing interest and/or missing the main points. Not sure where the best balance lies! Please edit as you think appropriate, and we can always argue afterwards about anything we think really matters. Cheers, Walkerma 18:06, 11 January 2010 (UTC)

Walkerma18:06, 11 January 2010

Does these three, somewhat reworded, points that I provided on the cellphone talk page provide any help in writting down a recommendation.

  • Ensure that there is an application suitable for mobile phones that can hold a large amount of articles
  • Compile a list of important and well written material for each country/region/language
  • Convince mobile phone developers to preload their phones with material from the list that corresponds to the country/region/language of distribution.
Dafer4519:03, 11 January 2010
 

I looked through some of the other 'Recommendation' pages - it seems Local Languages has the best format. The 'Strategy' section is what contains our recommendations - the Assertions, etc. are just to back it up.

So we write a Question, and answer it in a Strategy statement.

I will try to refactor our pages along that way.

Wizzy20:26, 11 January 2010
 

Dafer45, thanks for pointing out that discussion - I would have missed it. I like the SMS suggestion, I added it to the main recommendation - the others I think we have covered.

Wizzy21:28, 11 January 2010
 

I really dislike the first strategy statement. It is specific to companies/products, and not to processes.

Suggest:

  • Support third party developers/providers of open offline storage standards (such as OpenZim), readers which use them (such as Linterweb), and proprietary offline solutions (such as WikiPock.)
  • Encourage development of non-internet distribution systems, eg. SMS article requests.
Amgine00:32, 12 January 2010