The list of brands out there with an app has a lot of girth to it, and is growing faster than a snotty little girl who just ate the 3 course dinner piece of gum. Unfortunately, not all of them are doing something unique, usable, or even all that interesting, and ends up being another case of “just because you can, doesn’t mean you should.” The most successful apps serve a purpose, fill a void, are radically different than anything else (Flipboard), or are successfully aimed at the community (Alien Blue)in which it was meant to serve. It’s a simple formula to imagine, but it’s incredibly difficult to hit center-mass, and most miss even the most carefully placed dog-targets.

It’s easy to look at huge numbers and say these are the brands that uncorked a whopper, I mean just take a gander at some of these numbers (which are likely out of date):

• Barclaycard - Waterslide - 9,800,000
• Zippo – Virtual Lighter - 6,000,000
• eBay - Marketplace - 4,600,000
• Audi - A4 Driving Challenge  - 3,500,000
• Bank of America - Mobile Banking - 3,000,000
• Coca Cola - Spin the Bottle - 870,000
• IBM/Amex - U.S. Open - 450,000
• Stanley Works - Level - 400,000
• North Face - Snow Report - 300,000
• vitaminwater - Sound Lab - 250,000
• Zipcar - Zipcar App - 170,000

At first glance you would say these guys all got it right, but you have to look a little deeper, and relate those numbers to the size of the user base, and the size of that Brands community. Naturally those companies with huge communities and ubiquitous brand recognition are going to have massive downloads. How else can you explain all of the downloads Coke, Spin the Bottle has received? That app is only slightly better than the iGlow stick app.

Now look at the Kmart and Sears apps, which are nothing more than another way to shop on your iPhone. What value does an app that all but replicates the shopping experience in Safari add to that brands community? Not much, and their 2.5 star rating reflects that.

So who has gotten it right? Zippo is an easy target for a brand that hit the mark. They have more than 6 million downloads on an app that basically does nothing, and provides no real value other than entertainment novelty. I know that sounds like a slam, but it doesn’t really have to be. It was something that fit perfectly into their community, and what a lot of people were looking for as a fun way to show their attachment to the iconic pocket lighter. Gap is another example with their 1969 Stream iPad app. It’s a well designed, well functioning advertising piece that is just fun to look at and flip through, and has a companion website; or the app is the companion to the website – either way, good jaeerb guys!

There are tons more, too many to list in fact, and a lot of them are really well designed and developed, and a lot of them are junk; but that’s okay. Even the failures are doing their job, and hopefully the brands are learning from them and working on doing a better job for the next rev. See, that’s the key here.

Everyone wants to be the next Angry Birds, or Victoria Secret Pink, but what they lose sight of is that they really need to just be themselves, and be true to the personality of their brand. Getting caught up in being the next “big thing” is only going to get you so far. Failure is always an option.

So what am I saying here? I’m saying do your homework, and eat your veggies. Do the research. Spend some money, and build something your kids would want to use. Find a void and fill it with your app. Do something ridiculous and borderline crazy just to see what happens. But know why you’re doing it, and it can’t be because your competitors are. If that’s the only reason, then you might as well just follow the rest of the Lemmings……

2D codes are becoming more mainstream here in the US, and there are more and more instances of them popping in your daily life. The problem is, most people still have no idea what they are or how to read them, and having half a dozen or more different types isn’t helping.

The newest code to hit the scene is JAGTAG, which I ran across for the first time in the latest Swimsuit Edition of SI. Calling this one a 2D code is sort of a misnomer as I see it though. In order to get the content, you have to shoot a picture of the tag, then SMS it to a number, which unfortunately (for them) costs me money. This is a decent idea for when you don’t have signal to just automatically grab the featured content from the code, but it adds another step, and as well know, people are lazy. Website Magazine uses yet another iteration from ScanLife which is just close enough to fool the average user to thinking that their existing QR Code reader would read it – but it doesn’t. So even though I have a subscription to this magazine at work, I have never followed one of these codes, since my readers won’t san them. There are others too, like ShotCode and Semacode, both of which are different still from a standard QR Code and proprietary.

The problem with these proprietary codes is that they are closed systems, and out of the 3 readers I have on my iPhone, none of them read any of these other codes. In fact, without licensing from all of these folks, I would have no way of making an app that would read them all, and even then there’s really no way I could make it available for free. And if it’s not free, at least for a 2D code reader, it won’t ever be ubiquitous. The marketing shlock behind all of these other codes is that theirs is better, unique and has some feature that makes it a good choice. They all tout their reach into the mobile market, and how they can be read by millions. Sure it’s possible, but not as likely as if they were simply using QR Codes. QR Codes have been around for nearly 20 years now, have a much broader reach than all of these other codes combined, and are completely open and free to generate. Free is the key component here.

There are plenty of cool examples of QR Codes out in the wild, and I have quite a few listed in these posts on my blog. Google, just a couple of months ago, created a new opportunity for popular business in the search results to display QR Code window stickers with their Favorite Places program. If I planning a campaign for my magazine, print advertising, or other promotion where a 2D code would be a viable component, there’s no way I would pay for a proprietary code on top of the advertising and development of the program. With marketing budgets being downsized on all fronts, why would anyone use a closed system that they can’t maintain themselves? Why should I pay someone else to create something I could create myself in less than 2 minutes, especially since no technical expertise is required to generate a QR Code. A great example is the generator at QRStuff.com – online, simple and versatile.

I can’t really fault these companies for trying to create a new way of building a code, and trying to make money from it, but I would have used QR Codes as the basis of it. They’re simply more ubiquitous and at the end of the day, you want the greatest number of people to be able to access the content behind the code, and having a closed system isn’t going to get you there.

I recently updated the FIB-U-LATOR app to have more excuses, and I’ve decided to add another update, only this time I am going to add support for expanded features that require the use of the SQLite Database available to the app in the SDK. Getting data out of the database is pretty easy actually, and it really doesn’t take much code to connect to, then retrieve data. Here’s a quick tutorial over at dBlog, but I’m getting ahead of myself.

Since I work with MSSQL all the time at the day job, I’m really accustomed to having a nice GUI to do all the work of creating and managing my databases, and I really have no inclination whatsoever to do any of those tasks at the command line. None at all, no thanks. It didn’t take me long to find this simple, easy to use GUI called MikeT’s SQLite Database Management Application. It is very basic, and simple, but you really don’t need anything more than that. It’s fast, simple to figure out, and jammed with a bunch of options. You can add encryption when you create the database, and has a dropdown to select the column data type while adding new rows to the table, you can even import data from a tab delimited file to create a new database.

I have some work ahead of me to get my current data into the new database yet, and ideally what I would like to be able to do is convert the plist file to a tab delimited file and just import it. Right now, I’m not sure how to do that. EditiX seems like it’s a good option, but I haven’t tried it. There’s also a big list of XML editors for OS X at XMacL. Oxygen XML Editor seems like a really powerful option, but it’s a bit pricey at $350.00 for a single license. I’d rather hand-jam all of the entries than spend that kind of scratch for an app to do it, I only have a few hundred entries anyway, so it wouldn’t be a horrible march of death to get it done the hard way.

More to come as I get further into this.

It’s no secret that I have another iPhone app in the works, and that it will be available soon. Although, I have been reluctant to give out a lot of detail simply because, well, I’m a bit paranoid. I will say that it involves Brent and I recording audio for playback in the app, and that it has been interesting working with audio on the iPhone.

The first thing I noticed straight away is that it’s easy to use files that are far too large for the iPhone to playback properly while working with .wav files. I started working with .wav files for two reasons. The first being that I have a ton of them, and that made it easy to drop files in to test with. Second, compressed audio files cannot be overlapped on the iPhone, so if you want them to play simultaneously, .wav files are your Huckleberry.

First, I needed a microphone that wasn’t going to sound like an AM Radio, so I went out (dispatched the wife actually – thanks dear) and picked up a Blue Snowball. As it turns out, the Snowball is every bit as good as the reviews says it is, and I would highly recommend it. With the Snowball plugged in, SoundBooth open, we were all set and the recording commenced. Recording the audio was easy the most enjoyable part of the project so far, once the app comes out, you’ll see why.

When we were finished, I ended up with about two dozen CD quality .wav files, which still needed to be trimmed down. The files ranged in file size from 300k up to about 1.2mb. I trimmed the up, but left them as dual-channel files and tried to get them to run in my app. Needless to say the files choked both my iPod and iPhone and needed to be optimized for them to work. I tried a few things, and didn’t get very far in SoundBooth, so I opened them up in Audacity and removed one of the channels and converted them to mono. I also took the time to trim the ends so there wasn’t a lot of unneeded dead-space. The files are all now between 20k and 120k in size, and still sound as well as they play.

I have two different players in action on a couple of views in the app, and one has a single track playing at a time using AVAudioPlayer. Through digging around in some of Apple’s sample code, and online info (particularly from iPhone Dev SDK) I was able to get it work.

Here’s the .h code:

#define kAccelerationThreshold	1.8
#define kUpdateInterval			(1.0/10.f)

#import <UIKit/UIKit.h>
#import <AVFoundation/AVFoundation.h>
#include <AudioToolbox/AudioToolbox.h>

@interface TauntViewController : UIViewController <UIAccelerometerDelegate, AVAudioPlayerDelegate> {

AVAudioPlayer		*_player;

NSArray				*soundArray;

BOOL				soundEnded;

}

@property (nonatomic, assign) AVAudioPlayer*	_player;
@property (nonatomic, retain) NSArray *soundArray;

@property (nonatomic, assign) BOOL soundEnded;

- (IBAction)playTheSound;
- (IBAction)resetSound;

@end

And the .m file code:

#import "SoundViewController.h"

#import <AudioToolbox/AudioToolbox.h>

@implementation SoundViewController

@synthesize _player;

@synthesize soundArray;

@synthesize soundEnded;

- (void)viewWillAppear:(BOOL)animated{

UIAccelerometer *appAccel = [UIAccelerometer sharedAccelerometer];

appAccel.delegate = self;

appAccel.updateInterval = kUpdateInterval;

soundEnded = YES;

// Load the array with the sample file

soundArray = [[NSArray alloc] initWithObjects:@"sound1", @"sound2", @"sound3", @"sound4", @"sound5", @"sound6", nil];

}

- (void)viewDidLoad {

[super viewDidLoad];

}

- (void)startPlayback{

if ([self._player play]){

self._player.delegate = self;

}

else

NSLog(@"Could not play %@\n", self._player.url);

}

- (void)didReceiveMemoryWarning {

[super didReceiveMemoryWarning];

}

- (void)viewDidUnload {

[_player release];

}

- (void)dealloc {

[super dealloc];

}

#pragma mark -

- (void)accelerometer:(UIAccelerometer *)accelerometer didAccelerate:(UIAcceleration *)acceleration{

if (sqrt(acceleration.x * acceleration.x) > kAccelerationThreshold || sqrt(acceleration.y * acceleration.y) > kAccelerationThreshold || sqrt(acceleration.z * acceleration.z) > kAccelerationThreshold) {

[self playTheSound];

}

}

- (void)playTheSound{

// play the sound file

if (soundEnded) {

soundEnded = NO;

int soundId = random() % soundArray.count;

NSString *newSound = [soundArray objectAtIndex:soundId];

NSURL *sound1URL = [[NSURL alloc] initFileURLWithPath: [[NSBundle mainBundle] pathForResource:newSound ofType:@"wav"]];

self._player = [[AVAudioPlayer alloc] initWithContentsOfURL:sound1URL error:nil];

[self startPlayback];

}

}

- (void)resetSound{

soundEnded = YES;

}

#pragma mark AVAudioPlayer delegate methods

- (void)audioPlayerDidFinishPlaying:(AVAudioPlayer *)player successfully:(BOOL)flag{

[self resetSound];

[player setCurrentTime:0.];

}

@end

This selects a random sound from the soundArray into the player every time you shake the device, so long as there is not a sound currently playing. A couple of things I had to do which I am not sure if it’s the best way to handle it or not is adding the initialization of AppAccel for the Accelerometer in the ViewWillAppear function so that it loads the correct sounds for the view being currently used.

With the optimized sounds, the code works great. I thought about trying the sounds at a higher quality, in stereo, and using MP3s, but I haven’t tried it yet. Honestly I’m not sure I will since the files are so small, they sound quite good, and I’m not sure if there would be anything to gain by using MP3s over the .wav files.

Like I said the app will be out soon, so I hope everyone will like it as much as I do.

http://www.youtube.com/watch?v=jNvo3dR3RIA

I saw this commercial for the first time last night, and the first thing I did was stop it, and tell the little lady that I damn well better be able to go to Geico.com and download that ringtone. I’m sure there was trailing’s off as I finished watching it and rewound it to listen to the ringtone again, but the gist is just that.

Since I had some free time today sitting and waiting around for an appointment, I decided to head out the on my venerable iPhone, and see if I could get it. And you know what? You can. Honestly, I am kind of shocked. Shocked in the way that I can actually go and do something so makes so much perfect sense that most people wouldn’t even think twice about it being available. Unfortunately, too often companies miss the boat, and someone along the way makes a bad decision to not do finish the implementation. That’s what this is too, it’s just another step in the whole campaign, not another extra, or silly download that most people don’t care about. Fact is, most people don’t care until you don’t give them the option that they expect to have – then they get all seven kinds of bent.

+1 internets to Geico. Great JJEEEOOORRRGGGHHHBBB!!!!

Even before I finally had an iPhone magically bestowed upon me (thanks to the fam!), I had a HP iPaq mobile player – and have been fascinated with designing and building sites for the mobile web. I’ve been designing and developing websites for more than a decade now, and while I wouldn’t say it’s old hat just yet, I do get into a routine often enough that it gets to be “been there, done that”, and can get a little tedious.

Mobile browsers have their own set of problems, and if you thought you had it rough with IE, Opera, Firefox, and Safari, then you’ve got another think coming my friend. There are so many variables with mobile devices that it is a real challenge to get it right, and it would be damned near impossible to do it across all devices. That being said, if you have a solid understanding of standards oriented design, then you have an excellent start.

Before you start building, the first thing you should do is examine your site analytics to determine who is on your site, what content they are accessing, and with what mobile OS and browsers. If 98% of your site’s visitors are using Safari on the iPhone/iPod, then why spend a lot of time getting it to look perfect on another device or devices? I’m not saying ignoring those other devices, but they would not be the primary viewer, so the bulk of the time should be spent developing for the primary target. Analyzing the site’s statistics will also tell you what content to focus on for the mobile site. Since bandwidth, screen resolution and speed are important on mobile devices, you should trim the fat of your site, and not delivering everything but the kitchen sink; that’s what your regular site is built for.

Once you have determined what platform(s) you are developing for, then you can start in on the design and build.  For the sake of argument, I am going to focus on the iPhone. Keeping in mind that the screen size of the iPhone is 320 x 480 (pixel size), work through the design and make choices based on those dimensions. Be sure to plan for large buttons too, I can’t tell you how much of a pain it is to hit some of the little text buttons on some sites, and even some iPhone apps. Take for instance this screen shot of the Facebook app, and the little text link you have to hit to view your post when someone comments on it from the update screen – that’s something you want to avoid. If you are in need of some inspiration check out Smashing Magazine, they have a truck-load of great information compiled. In specific I recommend these two articles; Mobile Web Design Trends for 2009 and Showcase of Designs Optimized for iPhone. Now is also the time to decide if you want to support both landscape and portrait modes in your layout.

Let’s assume you have your layout planned out now, and are ready to start coding.The first thing you should code and implement is a way to determine if your visitor is on a desktop or mobile device, and I have some code that works quite well. In a post from earlier this month, I showed off some code I have been working for mobile device detection in .net. Of course not everyone is a slave to Microsoft, and I really don’t use much of it outside of my day job, so having something for a PHP solution would be handy as well. I found some useful PHP and JavaScript code earlier this year as well.

Of course, there are also specific elements you need to add to the head of the page(s) to ensure that your site fits properly within the viewport of the iPhone, otherwise your site will scale by default in Safari, and not look or work as intended. The first meta tag viewport, does just that and ensure a proper fit, while the second simply includes an image for bookmarking.

<head>
<title>iPhone site | hooray!</title>
<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0;" />
<link rel="apple-touch-icon" href="/media/images/site-logo-icon.png"/>
</head>

This is the bare minimum, mind you, and there is more that you can code in page if you want deal with orientation as well. Here’s another great post from Engage Interactive on building a website for the iPhone. The majority of the site should just be well written, valid code and you will be able to support the iPhone and beyond.

For you WordPress folks out there, WPTouch. It’s a great plugin that transforms your blog into an iPhone application styled site. I’ve had it running on Flogging English for a few weeks now, and while there are some plugin incompatibilities, it handles that well and I haven’t had any issues with WPTouch not working.

Back in June I wrote about supporting mobile devices with JavasScript and CSS, and at my day job we have been tracking a very significant growth pattern of mobile devices accessing our core domain, so it’s time to take some real action and work towards much better, more streamlined support of these platforms.

I’ve worked with a variety of tool sets recently to accomplish too, on twanonymously.com I integrated PHP mobile device detection to redirect to m.twanonymously.com for a mobile device. What I haven’t finished there yet though, is the design. It’s basically the same thing with some CSS alterations to maintain consistency. But that will come later. At my day job, we are a .NET shop, so I have to find a better solution, one robust enough to handle the 1.2 million daily pageviews we serve up.

The code I am working, started from code I found over here at Web Design Blog, and I have been modifying it to cover a few more devices, specifically ones that are in our top 10. iPod and iPhone are the top two, in that order, followed by T-Mobile Sidekick, and then Android, and after that…. the Sony PSP. Go figure on the PSP. So these are the devices in need of immediate support, and luckily they are all similar in screen dimensions, so no drastic changes for each platform need to be made.

What I’m still working on is trying to figure which devices actually identify themselves as a mobile device when you use IsMobileDevice. So far, iPod, iPhone, BlackBerry do not. My Windows Mobile does though, and I don’t know about the PSP or Android as I have neither. Here’s a link to a test page I have set up so you can see the output. If you feel like testing a device, feel free to post the results in the comments.

Here’s the code I have so far:

<%@ Page Language="C#" ContentType="text/html" ResponseEncoding="utf-8" %>

<script language="c#" runat="server">
protected void Page_Load(Object Src, EventArgs E){
if (Request.Headers["User-Agent"] != null){
if (Request.Browser["IsMobileDevice"] != null &amp;amp;&amp;amp; Request.Browser["IsMobileDevice"] == "true"){
// MOBILE DEVICE DETECTED --------------------------------------
DeviceType.Text = "Mobile Device";

// CHECK USER AGENTS STRINGS FIRST --------------------------------

if (Request.UserAgent.ToLower().Contains("windows")){
DeviceName.Text = "Windows Mobile";
} else  if (Request.UserAgent.ToUpper().Contains("MIDP") || Request.UserAgent.ToUpper().Contains("CLDC")){
DeviceName.Text = "Other";
} else  if (Request.UserAgent.ToLower().Contains("psp") || Request.UserAgent.ToLower().Contains("playstation portable")){
DeviceName.Text = "Sony PSP";
}

} else if (Request.UserAgent.ToLower().Contains("blackberry")){
// DOES NOT IDENTIFY ITSELF AS A MOBILE DEVICE
// RIM DEVICES (BlackBerry) -------------
DeviceType.Text = "Mobile Device";
DeviceName.Text = "BlackBerry";

} else if (Request.UserAgent.ToLower().Contains("iphone")){
// DOES NOT IDENTIFY ITSELF AS A MOBILE DEVICE

// IPHONE/IPOD DEVICES ------------------
DeviceType.Text = "Mobile Device";
DeviceName.Text = "iphone";

} else {

// NOT A MOBILE DEVICE
DeviceType.Text = "NOT a Mobile Device";

}
}

// SPIT OUT A BUNCH OF STUFF -----------------------------------------
System.Web.HttpBrowserCapabilities browser = Request.Browser;
string s = "<strong>Browser Capabilities</strong><br />"
+ "Type = "                    + browser.Type + "&amp;lt;br /&amp;gt;"
+ "Name = "                    + browser.Browser + "&amp;lt;br /&amp;gt;"
+ "Version = "                 + browser.Version + "&amp;lt;br /&amp;gt;"
+ "Major Version = "           + browser.MajorVersion + "&amp;lt;br /&amp;gt;"
+ "Minor Version = "           + browser.MinorVersion + "&amp;lt;br /&amp;gt;"
+ "Platform = "                + browser.Platform + "&amp;lt;br /&amp;gt;"
+ "Is Beta = "                 + browser.Beta + "&amp;lt;br /&amp;gt;"
+ "Is Crawler = "              + browser.Crawler + "&amp;lt;br /&amp;gt;"
+ "Is AOL = "                  + browser.AOL + "&amp;lt;br /&amp;gt;"
+ "Is Win16 = "                + browser.Win16 + "<br />"
+ "Is Win32 = "                + browser.Win32 + "<br />"
+ "Supports Frames = "         + browser.Frames + "<br />"
+ "Supports Tables = "         + browser.Tables + "&<br />"
+ "Supports Cookies = "        + browser.Cookies + "<br />"
+ "Supports VBScript = "       + browser.VBScript + "<br />"
+ "Supports JavaScript = "     +
browser.EcmaScriptVersion.ToString() + "<br />"
+ "Supports Java Applets = "   + browser.JavaApplets + "<br />"
+ "Supports ActiveX Controls = " + browser.ActiveXControls
+ "<br />";

DeviceStats.Text = s;

// SPIT OUT THE WHOLE USER AGENT --------------------------------------------
DeviceAgent.Text = Request.UserAgent;

}

</script>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Mobile Device detection</title>
<style type="text/css"&>
body{color:#666;font:76% Tahoma, Geneva, sans-serif;}
strong{color:#000;}
#mobile{margin:10px; width:365px;border:1px solid #060;padding:5px}
#stats{margin:10px; width:365px;border:1px solid #CCC;padding:5px}
#agent{margin:10px; width:365px;border:1px solid #000;padding:5px}
#device{margin:10px; width:365px;padding:5px;color:#000;font-weight:bold;font-size:1.5em;}
</style>
</head>
<body>
<h1 id="device"><asp:Label ID="DeviceType" runat="server" /></h1>
<div id="mobile"><asp:Label ID="DeviceName" runat="server" /></div>
<div id="stats"><;asp:Label ID="DeviceStats" runat="server" /></div>
<div id="agent"><asp:Label ID="DeviceAgent" runat="server" /></div>
</body>
</html>

I just returned home yesterday from the first ever FITC Mobile up in Toronto, and if I was still of the drinking persuasion, I would raise a pint to Shawn and all of the other amazing FITC staff and volunteers who makes these events so bloody awesome! Every one of the events I have attended from them is amazing. Flash in the Can is always my favorite, but they are all top notch. The David Carson workshop a couple years ago was brilliant.

I always come back from these things energized and ready to take on the world again with new ideas and exposure to all sorts of tools, designs, people, and technology that I hadn’t heard of knew little about. FITC Mobile was no exception. The top 3 for me were sitting in with Dom Sagolla, Brady Gilchrist, and of course, Colin Moock. The only real down side is figuring out how to make all (hell, I’d settle with one or two) of the things swimming around in my cranium become some semblance of a reality.

The coolest thing I learned about was MegaPhone. So basically, it’s a Flash built gaming engine that allows players to call in using a mobile or standard phone and play games against multiple players from any location. They have some great things going on, have some cool games and more information on their site. I would love to get something like this going at work.

Being a mobile conference, there were a lot of sessions on iPhone dev and marketing, but they ran the gamut from Blackberry, to Windows Mobile. One things that I will be using on my next app will be Titanium Mobile from appcelerator. Titanium Mobile allows you to build native iPhone and Android apps using HTML and JavaScript, and it looks really cool. Just the other day, a friend of mine Ryan, sent me a link to an article about using .NET to build iPhone apps.

So now I want to be able to build simultaneously to iPhone and Android, so I will need an Android phone. I also have ideas for about 6 more iPhone apps, a couple of web sites, and some other things as well. Great. Last time I checked I’m just one dude who already has a full-time gig. I guess I’m going to have to prioritize a few things.

Now if only I can figure out how to squirrel away another extra 3 or 4 hours in the day, I’ll be all set to make millions…..

A picture is worth a thousand words, or maybe just 99 cents! As of just a few minutes ago, FIB-U-LATOR went live in the app store.

Thanks to everyone for help, encouragement, sarcasm and most of all…. excuses! DOn’t forget to sign up on the Facebook fans page too, it’s been a lot of fun (and work) to get here, and I’m really excited. If you couldn’t tell….

Check it out, buy it, and give awesome ratings!

Get FIB-U-LATOR from the App Store.