Fit more apps onto your Android phone storage

Some Android phones (yes, I’m talking to you, HTC Desire) have a pitiful amount of storage available on the phone itself for storing apps, so here are some tips to allow you to shoe-horn more apps onto your phone (though, paradoxically, this does involve installing more apps on your phone, though all the apps mentioned below are free!).

Note, on an Android phone

• "Memory" typically refers to RAM memory (the memory used temporarily when an application is running, which gets wiped when you turn off your phone), and
• "Storage" to app storage space on the phone and also and the SD card (where apps and their data are permanently stored).

Tip #1
Install App 2 SD or a similar app. This app allows you to move some apps to your phone's SD card (if the app developer has allowed it), which typically has lots more available space than the phone itself. It also alerts you if you install a new app and that app can be moved.


Tip #2
Install DiskUsage and choose to view "App Storage". This will show you how much storage is used by each app on your phone. Each app will use the storage for either:

• apk: This is the actual app. Some apps can be moved from to the SD card to free up space - see above.
  
• Data: Application data. For some apps, it may be safe to delete this data if it grows too large - see below.
  
• dalvikCache: This means the app is stored on the SD card, but part of it is also taking up space on your phone's own storage.
  

The apps are listed in order of how much storage they use, so you can pick out apps worth deleting.

Tip #3
Install Uninstaller app. This lists your apps in order of storage used, and also indicates which are on the phone and which are on the SD card (though note that if an app is marked as being on the SD card, it may also be using space on the phone for the “dalvikCache” - see above - in which case removing it from the SD card may also free up space on the phone itself).


Tip #4
The "Data" space for some apps seems to just grow and grow, in particular the official Facebook and Twitter apps. For both these apps, I have on numerous occasions deleted the data for the app with no significant ill-effects that I have noticed (but you do this at your own risk!)

To delete app data, go to Home > Menu -> Settings -> Applications -> Manage applications, find the app, and tap "Clear Data". (Of course, this is not advisable for apps which store data on the phone only, since you will lose all your data!)


Tip #5
Install 1Tap Cleaner or a similar app that allows you to delete data that apps cache on your phone. Clearing this data usually has no bad effects, but any space you free up will gradually get used up again as data is re-cached, so this is only a temporary solution.

Google already crawling & indexing AJAX sites?

In October 2009, Google proposed a new standard for AJAX web sites that would help search engines crawl and index the content.

Now it seems this may already be (partially) live?

But it's still not clear why each web site must have its own "headless browser", instead of Google's crawler just having it's own headless browser.

A better way of reading magazines/news online?

Your average news/magazine website is fine when it comes to drilling down to specific articles, but wouldn't it be nice to be able to read an online magazine in a way that was closer to the way we read (or just flick through) the physical version?

Mag+ Concept Video
Matt Jones and Jack Schulze at BERG have produced a concept video of a future digital magazine reading experience for Bonnier R&D. Kicker Studio is working with Bonnier to expand this concept into a robust, interactive prototype over the next several months.

While you're waiting for the Mag+ to be designed, built and delivered, try out Google FastFlip, "a new reading experience that combines the best elements of print and online articles".

Web development "tools of the trade"

A useful round-up of Web development frameworks, covering server-side and client-side (JavaScript, CSS, animation):

Tools of the Trade: Web Development Frameworks that the Pros Use

It doesn't cover Javascript templating frameworks though, such as:

• pure
• Closure Templates
• EJS
• UIZE
• jTemplates
• mjst
• JavaScript Templates
• Ajax Templates
• prototype Templates

These frameworks provide a way to transform Javascript data/JSON into HTML, in the same way that XSLT can be used to transform XML into HTML.

It seems the jury is still out on whether the "fold" matters or not...

The Fold Doesn't Matter
User Experience and Design, Wed 16th Dec 2009

"Over the last 6 years we’ve watched over 800 user testing sessions between us and on only 3 occasions have we seen the page fold as a barrier to users getting to the content they want."


Browser Size: a tool to see how others view your website
Google Blog, Wed 16th Dec 2009

"On the download page for Google Earth, the install rate increased by 10% when we moved the "Download" button 100 pixels upward."


It may be best to play safe and use Google's new BrowserSize tool

Badly written email subject lines

I just received a renewal reminder email from my travel insurance provider, www.multitrip.com

You might imagine the email subject line would be something like:

Renew your worldwide travel insurance policy for just €39.99

Instead it's:

AMT Renewal - Ref:[AMTXXXX/nnnnn] - REMINDER 1

multitrip.com badly need to learn how to write microcontent.

Patching code in an aspx.cs file, without rebuilding

You've just built, tested and gone live with a new build of your ASP.NET web site when you discover a bug in thispage.aspx.cs. Your next build/test/release isn't planned for a few weeks, but the bug needs to be fixed now, if not sooner. What to do?

If the bug was in thispage.aspx, you could simply fix it and apply the new page to the live site as a patch, knowing that it won't affect any other pages on the site. Since the bug is in the code-behind file, you can't do this without a full build and associated testing, etc.

Solution:

Copy the code from thispage.aspx.cs to thispage.aspx (put the code in a <script language=CS runat=server></script> tag), and make these changes to thispage.aspx:

• Remove the namespace / class declaration
  
• Remove any declarations of controls as variables
  
• Change any "using" statements to <%@ Import ... %> statements
• Remove "Codebehind" and "Inherits" attributes from <%@ Page %> tag

That's it (more or less). Test and deploy thispage.aspx as a patch to the live site.

Then for the next full release, fix the bug in thispage.aspx.cs and remove the above code from thispage.aspx.