Today, we pulled back the curtain on our next product: Uberdeck.
Uberdeck is a service that allows mobile app developers to send marketing campaigns straight to their mobile apps, letting them reach their mobile app users directly, for cross-selling new apps, providing notifications of upcoming features, etc.
With traditional desktop applications, software vendors have long been able to generate significant revenue by selling new products, or new versions of existing products, to their existing customers. One way this was done was by sending an email marketing campaign, perhaps using a service like Campaign Monitor, to their customer list.
With mobile apps, this avenue of marketing is largely nonexistent, as the app users interact with the mobile app stores almost exclusively, and there is rarely an open channel of communication between the app user and the app maker.
Uberdeck attempts to fill this gap, giving mobile app developers an opportunity to create a more direct way to market to their existing customers.
Uberdeck has been in development for quite some time. We are now entering beta, and are accepting signups for the private beta launch.
More info is available at www.uberdeck.com
Throwing a birthday party for a 1 year old isn’t so much about throwing a party, as it is about finding a delicate balance of variables that will keep one baby, two dogs, and a handful of over-enthusiastic adults happy for a short while.
Mommy made a smash cake for us – Ethan’s favorite color (mine too).
Ethan being all 1 and stuff.
A good time was had by all!
“If a hunted cat, surrounded and hard pressed, turns into a lion, God knows what I, who am a man, may turn into.”
- Sancho Panza, Don Quixote, Book 2, Miguel de Cervantes.
Last night, the drive holding all of our source code for the last 8 years died a pitiful death.
Luckily, we had all of our data backed up to S3. Arq saved our asses with a complete, flawless restore.
During the process, I had a chance to look over the complete source code repo, taking the opportunity to prune some things and clean things up a bit.
Just for fun, here’s a listing of all of our products, give or take a few, since the company was founded in 2005.
Once in a while, the CEO of a large organization, let’s call her “Leslie”, purchases one of our apps.
When she has a problem, the support ticket we get is never from “Leslie”. It’s usually from “Steve”, the assistant to the executive assistant of the person in charge of the IT department. By the time we get the email, it has made its way through 6 people in the organization, 2 separate internal help-desk systems, and is already 4 days removed from the time “Leslie” sent the original email.
We received one such email from “Steve” recently. “Leslie” noticed that our spam filter app wasn’t filtering spam as well as it should. She wanted to know why.
I requested that someone click the “send debug” button inside the app, so that I can take a look at the debug log and find out what’s going on.
Two days later, a response arrived from one of their internal help-desk systems. A ticket has been opened requesting that someone click the “send debug” button.
Five days later, the second response was an update from another internal help-desk system, notifying us that several members of the IT department, and at least two executive assistants were added to the ticket requesting that someone click the “send debug” button.
The debug log arrived 2 weeks later.
The first line in the debug log revealed that the application was turned off.
Thirty seconds after receiving the debug log, I sent a response explaining that the application was turned off, and providing instructions for how to flip the ON/OFF control in the app settings to ON.
Two days later, a response arrived from one of their internal help-desk systems. A ticket has been opened requesting that someone “flip the ON/OFF control in the app settings to ON.”
- “Leslie, do you like that spam filter app?”
- “You know, the app is great, but you have one problem, and it takes a month to get a response from those people!”
“At one point, somebody kind of looked at the process to see, well, what it’s doing, and what’s the overhead built into it. What they found is that, [at IBM], it would take at least nine months to ship an empty box.” ~ Rich Seidner, former IBM programmer. Triumph of the Nerds.