We thought we would share this because sometimes Verizon gets the rep for being a bit pricy on new phones (which is true sometimes), but this time, it's T-Mobile going over the top with release date pricing on a new phone.
It is usually not a surprise when a carrier does things a bit differently from the other carriers when they are selling the same phone. For example, last year there were multiple names for the Samsung Galaxy S II on the different carriers, and of course each carrier might add on their specific package of bloatware. However, today's confirmation coming from T-Mobile regarding their version of the Samsung Galaxy S III is most assuredly a shock, and will likely make your back account recoil in fear.
For some odd reason that we can't fathom T-Mobile is selling their version of the SGS3 for a whole lot more than the other carriers. Without fail so far, the other carriers have announced pricing at $200 bucks for the 16GB version and $250 for the 32GB version. That is not the case with T-Mo. Here is their confirmed pricing plan,
Starting tomorrow, T-Mobile will offer the Samsung Galaxy S III in 16GB or 32GB memory options paired with T-Mobile’s Value or Classic service plans.
Available with a qualifying Value voice and data plan with a two year service agreement, the Galaxy S III will cost an out-of-pocket down payment of $229.99 (16GB) or $279.99 (32GB) with 20 equal monthly payments of $20 per month via T-Mobile’s Equipment Installment Plan (EIP).
Also offered with a qualifying Classic voice and data plan, the Galaxy S III will cost $279.99 (16GB) after a $50 mail-in-rebate card or $329.99 (32GB) after a $50 mail-in-rebate card with a two-year service agreement.
So... basically, if you want to get the 16GB SGS3 you will initially have to pay $329.99 and then wait for a $50 dollar mail-in rebate, or $379.99 before the mail-in rebate for the 32GB version. That is a whopping $130 bucks more at the time of purchase than any of the other carriers, and still $80 bucks more after you get the rebate back. Is there something wrong with this picture?
Source: S3Forums via AndroidCentral and Engadget (pic)