|WikiProject Computing / Software|
Mobile applications 
Internal consistency issue: the mobile applications section currently assumes that the definition of "site-specific browser" is the more specific meaning previously given to "general purpose site-specific browser"... there are certainly many mobile applications for iPhone and Android, if not other platforms as well, which consist of dedicated web browsers for a single website. 188.8.131.52 (talk) 16:45, 5 July 2010 (UTC)
GreaseMonkey, augmentation and task-specific/domain-specific browser tech 
The Greasemonkey article is now more informative in the section Equivalents for other browsers.
We need to re-design this article in terms of site-domain-task.
When I am running Mobi, Rikeichan, Rikeisama or PeraPera on FireFox, my browser becomes a different tool because those extensions work in Text Areas on my own local web pages. One unexpected result is that they render Google Translate otiose.
Those evolving plugins/extensions conflict with each other on Firefox - just one exmaple of how far we have to go in such a simple thing as a non-Japanese web user having an effective user experience at Japanese web pages or non-Japanese pages devoted to Nihongo content such as Haiku at wikisource or wikibooks.
Those extensions also have word list options - something which flashcards-in-the-browser are slow to adopt for web language learners (and so my continued interest in Curl programming language CSPD.)
None of the current changes involve add-on's for Text tasks which are themselves written in smart text-oriented languages such as Icon (Unicon, Object Icon) or smart parsing languages such as PEG-equivalent Rebol or rule languages such as SWI-Prolog.
Strikingly, for me, no Smalltalk variant has yet produced a browser (and the Squeak Sophie e-text project appears to have failed.)