Telstra Mobile Overseas Data Charges

imageYou need to be very careful of the data charges while roaming overseas. Not because the charges are ridiculously high at $16 per meg. But because Telstra Australia lie about the amount of data you download.

I recently opened a 0.387 meg data connection while roaming in the USA. Only to be charged $92.39 for the privilege.

Lets just say hypothetically that I did not know exactly how much data I was downloading, and ripped into the maximum possible data that could have been downloaded in the 1:23 (1 min 23 seconds). I could not have downloaded that amount of data on a 3 G Connection even if it was a good connection and not the CRAP T mobile service that is on offer in LA.

So bottom line. They cheat you, and don’t provide you with proof or even the data downloaded in that time.

Apple or Android app development

It’s funny, that when we tell people we are now developing Apps for the iPhone and iPad, we get a response… “What about Android” They have a bigger market than Apple.

While technically the Android is gaining ground fast, it would appear that owners of Android products don’t actually use them!

Here is an extract of some data from Google Analytics about the use of iPhone, iPad and Android devices. on 15 March 2011.

image

Notice that there is one category for Android devices. If you lump the iPhone and iPad devices into one, you get a massive    1345 vs 153.  or a whopping 11% for Android. Now if you were us and developing for a market. Would you go for the 11% market that Android has?

So Android lovers, either get on your mobile devices and browse / buy like crazy, or accept that fact that your device is less used in the real world than you would like!

Part 4: Talking to an asmx web service – A .net developer learns objective-c for iPhone iPad

So here i am reading up on how the cocoa touch framework doesn’t have support for working with xml too easily and its not an easy task to undertake in manually parsing a soap xml… when along comes something so amazing i may have wee’d my pants a little.

Behold http://sudzc.com

SudzC is an amazingly helpful website where you simply pass it a url to an asmx or upload a wsdl file, it spits you out a fully fledged example project along with reference documentation and the source code you’ll need to include to make webservice communication as easy as…

image

Important stuff is the:

[service … line and the Completed action (or event in .net speak) it returns. I simply just spat some stuff out to the log to see some results.

What’s is awesome and worth mentioning (again) is what is in ws.iPhone.zip\Source\Examples. From within the zip you get sent from SudzC is the all important examples you need to start cracking (with YOUR webmethods).

SudzC … i think i’m in love!

Part 2: Nappies and training wheels – A .net developer learns objective-c for iPhone iPad

Just going through some early podcast videos from the Cocoa Touch Netcast www.cocoatouchnetcast.com (search cocoatouch netcast in the itunes store).

The first video is good going off the back of the videos mentioned in my last post. The 2nd video ep 2: Slider is also helpful. It clearly explains Class inheritance (a class is your code, classes can be inherited from super classes bringing with it certain functionality), actions and outlets (the way which the UI interacts back and forth with the code) and a good demo of a basic slider control flinging left to right adjusting with it the text in a label of the sliders current position. A good hello world (without the text hello world).

Have a good pause at 11mins into it for a good screen explaining actions and outlets.

[ViewController]
outlet -> points to label
action -> references a slider’s event

So the code in SliderViewController.h would look something like:

#import <UIKit/UIKit.h>
@interface SliderViewController : UIViewController {
UILabel *sliderLabel;
}
@property (nonatomic, retain) IBOutlet UILabel *sliderLabel;
- (IBAction)sliderChanged(id)sender;
@end

And with any .h file there is a matching .m file, SliderViewController.m would look like this:

#import "SliderViewController.h" 
@implementation SliderViewController 
@synthesize sliderLabel; 
-(IBAction)SliderChanged(id)sender { 
UISlider *slider = (UISlider *)sender; 
int progressAsInt = (int)(slider.value + 0.5f); 
NSString *newText = [[NSString alloc] initWithFormat:@"%d", progressAsInt]; 
sliderLabel.text = newText; 
[newText release]; 
} 
-(void)dealloc { 
[sliderLabel release]; 
[super dealloc]; 
}

Armed with limited knowledge (feel free to correct me) I see variables and methods are referenced in the .h file (variables within the {}’s and methods after). Naming a variable (ie sliderLabel) the same as the outlet seems to give you the ability to speak directly with the label on the UI.

You need to call @synthesize to be able to use the sliderLabel variable on the .m file. This I assume from the example is to be called for every variable mentioned in the .h file.

So … time for me to do some damage. Stay tuned, lets see if I can remember to alloc, init and release!

Part 1: Baby steps – A .net developer learns objective-c for iPhone iPad

What is this?
A series of blog posts about a staff member at InteractiveWebs (.net developer since .net went 1.0) taking on the challenge of transitioning to iPhone and iPad development.

Brief context:
Every day we live with "Object not set to an instance of an object" or "modify the web.config" this or "I’m not a xaml designer" that. Hang on a second, if I am frustrated by using Microsoft technology well developing for it is equally frustrating. But if using Apple technology is the equivalent to geek crack, then I wonder if developing for Apple and its devices are an equally enjoyable experience.

Where am I at?
Had a play with Monotouch http://monotouch.net and it seems like a logical step for someone like me. However it did dawn on me that I’m trying to move away from the .net way of life so in a way monotouch seems a bit of a cop out (while I am a big fan of what those guys are doing).
Its been a few days of downloading sdk’s and watching demo videos. Already getting itchy to jump in to some code.

First things first. Bookmark, Favourite and Pin to home screen http://developer.apple.com as this site is amazingly helpful. (You don’t even need to read dreaded …. Whitepapers)!

Here you will find everything from surprisingly helpful documentation, videos and the iPhone OS SDK (this includes once downloaded xcode, xcode is your new visual studio). You will need to create a developer account, no problem it just attaches on to your existing itunes account. Brilliant!

On this page http://developer.apple.com/iphone/index.action click on the "Getting Started Videos". It will open up itunes allowing you to download some great videos to iTunes U. My next steps which were very helpful were to watching the following videos:

  • Introduction to the iPhone SDK
  • Key practices for iPhone Application Development
  • Fundamentals of Cocoa Session from WWDC

That last video I suggest watching very slowly, rewinding as much as you need to letting it all sink in. It was this video where things began making sense.

That’s it for the first post. Next will likely be jumping in to Views and kicking off a traditional "Hello World".