Why NOT to Ditch Your Crappy Old Smart Phone


Like many people out there, I was pumped when I got my first flashy, sleek, touch-screen-having smartphone.  A Samsung Acclaim was my entry level purchase.  The "new phone" haze soon wore off as I realized this was a bulky, slow, laggy beast of a device.  The UI was so laggy, there were times I almost missed calls from not being able to swipe the answer button.  I pity the soul who would need to use this phone for an emergency call.  Imagine my glee when my cell phone carrier accidentaly put me in the system for a new phone 6 months early.

Rather than sell the old phone on ebay or craigslist, I put the battery vampire back in its little coffin-box where it could torture me no more. The only reason I let it lurk in storage was incase I took my shiny new phone for a swim, or accidently gave it a good cement bashing.  Usually the phone would sit there for a few years until I retired my current phone, then I'd throw it away.  This all changed a few weeks ago.

I was asked by my mother-in-law to fix up an old Dell.  She wanted a laptop for her new coffee shop to play Pandora.  After a few hours of messing with DSL, and trying to configure wireless drivers, I decided ressurecting the dinosaur of a laptop was just not worth the effort.  As I went to skip the song I was listening to on Pandora (on my shiny new phone), I was hit with a brilliant idea.  Why not let her use my the old Acclaim for a Pandora / Slacker Radio / Twitter device?  It has wifi capability, so no service plan needed!  I loaded up her account on the old phone.  The UI was even more slugishly painful to use now that I was used to my new phone.  After downloading Pandora, Slacker Radio, and Twitter, I was rocking away to "Alan Parsons Radio" in no time (take that Gotye).

Since I have two of these monsters (my wife had one too), I gave one to my mother-in-law, and decided to put the other to work for me.  Now I can listen to Pandora without being interupted by emails and phone calls, and  I don't use up bandwidth on my dataplan.  There also does not appear to be a "Yes I'm still listening." feature on the version of Pandora the old phone uses (bonus!). I could use the Roku, but then I'd have to go through my TV (I don't have a receiver.)



Here are some new devices your old phone can become:
-Awesome Internet Radio Device
-Good Roku Remote (Many free apps for this).
-Crappy Storage Device
-Crappy Camera (Transfering by bluetooth is nice though.)
-IPod Wannabe (Not as good, but it does the job.)

So, now I send you on a quest:
-Send me an email detailing your recycled uses for an old smart phone. (At least 1 pic needed.)
-I'll do a follow up post in 2 weeks with the best submissions!

Comments

  1. Geek GirlApril 26, 2012 at 4:34 AM

    I think this is great! For me, though, I donate my unwanted phones to either the troops defending our country or the women's shelter. Found you via our bloggers group for Blogger Effect. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Phoenix LiveView: Async Assign Pattern

Image
I've been using LiveView for about two years now. It's a great framework that makes snappy and responsive pages. One anti-pattern I see fairly often is loading a lot of data in the initial page render. For the un-initiated, the mount/3 function is called twice.  Once for the initial 'dead' render, and again after the socket is connected.   Many times, for the sake of simple straight forward code, not much is done differently between these two renders. I haven't found any references (I'm sure they exist) on a best practice for managing the following flow: Set sensible, lightweight default values on initial render. Kick off one or more async processes to make longer running function calls. Receive the values in the LiveView, and update the assigns. As always in Elixir, the tools are powerful, and theres many ways to accomplish this. Spawn a linked, or unlinked process. Start a supervised, or unsupervised Task. Make a call to a GenServer, and have it send a mess
Read more

Write Admin Tools From Day One

Image
UPDATE:  I gave a talk expanding on this blog post at EMPEX NYC 2023 . The Problem Writing useful features for your users is key to a successful product.  It makes sense then that you should maximize your time writing features for those users.   This approach is very effective at the beginning of a product's life, but over time, you may find you are spending more time maintaining the product that developing it. Some of the biggest development time sucks can be: Tracking down the cause of unexpected behavior. Fixing data. Answering user, or team member questions. Running maintenance scripts, or other ad-hoc tasks. The "Oh #&@$" Solution These small support tasks start to add up, and there is no easy way to offload the work to product, or support.  You and your development team reach a breaking point where you must start prioritizing administrative tools. Unfortunately, you will slow down your new feature development even more in the short term.  It will take time for t
Read more

Custom Kaffy Styling

Image
I recently gave a talk at Empex NYC ( link to talk ) on why you should be writing admin tools from day one .  In my talk, one thing I highly suggest is to make it very obvious what environment you are in when providing a web admin UI for your team.   We've been using Kaffy at SwayDM since the beginning.  At the time, you couldn't easily overwrite the styling.  I maintain a private fork of Kaffy for changes I've made, which included the ability to change the background color. I recently merged the past few minor Kaffy releases back into my fork, and saw that Kaffy now has the ability to provide Extensions which allow you to inject custom html, css and javascript.  I spent a little time making a custom CSS file to change the color of the Kaffy nav, and add a title which notes which environment you are in. For each environment, I have a static file for CSS styling overrides. kaffy-ext-local.css kaffy-ext-staging.css kaffy-ext-production.css defmodule SwayDMWeb.Admin.Kaffy
Read more