Redshirt Labs

What are we doing next?

2011-03-06T10:42:00.000-08:00

This is a question that we've been struggling with quite a bit. Should we keep adding more features to Zengaku? Would a new platform such as the iPad, or Android make sense? What about some of the smaller platforms where we wouldn't get lost in the noise? The WebOS looks interesting and RIM holds a special place in our hearts since it's just down the road and a number of our ex-coworkers are there now. Even one of the original Redshirt's works at RIM. But the platform seems to be a bit dense to penetrate and we're not hearing great things about the opportunities for small independent developers. But that's probably a whole other blog post.

Some of us are very excited by the idea of doing independent mobile games, others feel like productivity applications would be more rewarding. Coming to a decision is pretty difficult. There are benefits to both approaches. Games don't require a lot of support and maintenance and if you make a popular game you can build on that popularity and revenue with a new version 2 or 3 of the game and customers generally are good with that as long as there is enough of a new experience. However productivity or utility applications seem to have different expectation. Our friend, Barry, the maker of LiveCams had told us in the past that support and maintenance were a major part of his overhead of selling his application.

However games are very hot and cold and require a real creative spark to be done well. We're all pretty much dedicated software developers, but we're not known for our artistic abilities, or our familiarity with Photoshop. None of us have built a real game before. Zengaku is a pretty simple game really. Any new game we might create will likely be a significant departure from this genre.

With a productivity or utility application you can have more opportunities to build the business beyond just the mobile market and sales are generally steadier. A productivity product usually will have a longer shelf life as well. Plus you get the satisfaction associated with knowing that the work you've done is going to help someone get something accomplished easier, or more quickly than they could previously. It's a hard choice, but we seem to be settling in on a direction for now.

Games FTW! Regardless of our personal deficits we all really enjoy games and are pretty charged up by the challenges in developing game software. Also gaming provides a relatively simple business model with a potentially better chance of success since a lot of small games have done quite well in the mobile marketplace by providing a fun, engaging and unique twist on a familiar gaming paradigm. Also given Zengaku's recent growth in popularity we'll be providing more frequent update to that game to see if we can get it up to where we believe it's true sales potential should be.

Complexity and Version 1.3

2011-02-26T15:40:00.000-08:00

Our latest update to Zengaku is out the door and actually moving pretty well by our usual standards. No one is breaking the bank just yet, but sales have been steady for the past week, which is nice.

We thought we'd share a bit about the things we found while working on this latest release.

Backwards Compatibility:

We've been trying very hard to ensure that older devices will continue to be able to allow our 10's of faithful users to play on their ancient iOS devices. In particular one of our developers/founders still has a 1st generation iPod Touch device running iOS 3.1.3 . It's been great for backwards compatibility testing. One issue we had was with our new back and settings buttons. The new buttons are simple images without any text. In our testing we found that the images were rather small so there were a lot of missed touches. I got frustrated more than once while trying to get into the settings screen.

The fix was pretty simple. We just had to adjust the size of the bounding rectangle around the button. This stretches the image out to fill the rectangle so we used IB to inset the image in smaller bounds inside the touchable area. However good old iOS 3.1.3 devices don't seem to adhere to such settings from IB. So even though newer devices worked like a charm and looked great we had one device where the gear used for our settings button was a tad oversized.

The solution to this new problem was again simple enough, just a bit of a pain really. What we've done now is created the image and the button as separate objects on the view. The button is completely transparent and our image is sized and placed under the button. This gets us better touch sensitivity and backwards compatibility.

Small Features Mean Big Increases in Complexity:

We added a number of small features in the 1.3 release including a game timer, a settings screen, social bragging, landscape orientation, sorted notes and automatic option removal.

None of these features on their own were particularly complex, but one in particular ended up causing a number of bugs and taking a lot more effort than we'd originally thought. Can you guess what feature that was? It was the game timer. You'd think that would have been simple right? It's a timer that counts how long you took to finish a game. How tough could that be?

Well it turns out that it's a fair bit tougher than you'd think. You have to think about the logic for calculating the time it took. We had to ensure that the timer was still counting time even though you might not have turned it on. So you couldn't just turn on the timer at the end and make it look like you finished the game in almost no time. We also had to make sure that if you left the game screen to view the options menu, read the help docs or just exited out to use another application the timer wouldn't keep counting. Seem simple enough except that there's a few different way to determine each of these transitions in iOS. The modal dialog we use for our settings is different than hitting the back button which is different than hitting the home button or the lock button. We had the added problem of the file format used to save games wasn't previously saving the game time properly. We'd had the idea of timing games from day one, but we'd never written anything that actually worked properly until now. So games you'd started previously might have quite odd times now. We corrected for that by updating the version on our file format so that if we detect a game that was saved with the older file format we'll assume the time is 0 and upgrade the file format.

The timer caused other issues in that once you won the game we had to make sure that the time you could brag about via Twitter or Facebook would be correct as well. Because our implementation of the time storage wasn't and probably still isn't particularly sound we had been re-calculating the time when you were on the win screen. This meant that any time that passed between you completing the puzzle and hitting the brag stone would show an increase in time. This too was addressed in our last update out just this week after being approved by Apple. One other little timer related tweak in our last update was to include the time on the win screen. It was obvious pretty quickly that including that on the win screen was an oversite that needed to be corrected. You did all that hard work to finish the puzzle quickly and then you don't get to see the time being recorded. Silly us.

Interface Builder is loads of Fun:

The interface builder is a nice tool and does help with the initial layout and prototyping a UI very quickly. However it seems that the more that we had to tune our UI to suite the needs of our desired gameplay we found the tool to be lacking. Anytime you need to actually need to deviate slightly from the default behaviour you have to jump back into good old objective C.

Not that coding is a particularly painful or foreign activity for us, but it seems like the tool's promise is greater than its delivery. It would be nice to be able to tweak the touch responses of UIButtonView's without having to create our own custom buttons views in code. But there was no option for us to easily modify the existing buttons to allow us to respond differently to a press and hold and a press using the standard controls. Also with the increased importance of handing multiple orientations in an application. It seems like something that the IB should support is the ability to prototype the landscape and portrait orientations for a single view controller and provide some simple animations for the components to transition between the 4 possible orientations. In stead we had to mock up the landscape view and then collect the co-ordinates of all the different elements and provide the code to translate them at runtime.

Conclusions:
Zengaku 1.3.x has so far been a very, very successful release for us. For some reason we've seen improved traffic for both the paid and free versions over the last 3 weeks. We're not sure if it's the new, price, the fact that its a sale, or if the added puzzles and retina images had anything to do with it. So far the timer seems to be getting better and we've only heard of a couple of issues from our users. The Twitter and Facebook integration was at least simple to add, but hasn't been used extensively so far based on searches we've done. It's too bad that more people aren't making use of those features and following Redshirt Labs on Twitter, or Zengaku on Facebook. We'd love to have more interacting with our user base so we could better understand where the game could and should be going. However with the improved overall reception we're pretty encouraged and a bit reinvigorated. We should be providing more incremental UI improvements over the coming weeks and I'm thinking that an iPad version is starting to make a lot more sense. Maybe in time for the actual launch of the new iPad 2.

But one thing we've learned is that small features or changes have a effect on complexity that is orders of magnitude above the complexity of the feature itself. The other thing we're learning is that advertising is a complete waste of time. We've not spent one dime on advertising in the past 3 weeks, but have seen a sustained improvement in our downloads that we've yet to really explain. However we're extremely happy to see the improvement. Keep playing!

Reducing the Scope

2011-01-26T05:40:00.000-08:00

We really wanted to put a lot into this next release of Zengaku. We'd had a number of ideas for features to do and we were really excited by the idea of native iPad support since the larger screen would make game play better for the full size puzzles in particular. However a lot of things have happened since our last release. Not least of all was the fact that we all lost our jobs. Then some of us left town in search of work, others have taken up at a real startup rather than our little side project. Finally some have just lost interest and would rather spend their free time on other things. So our resources have dwindled and our attention has been divided. Recently I had my first child which also reduced my energy and free time. The core red shirts is now numbering 2. Maybe 2.125...maybe. So something had to give.

A quick analysis of our installed user base shows us that only about 4% of those who've downloaded Zengaku are playing it on an iPad. That's a pretty small base to be targeting a good chunk of our effort. In fact when you do the numbers our iPhone version is actually also probably not worth the effort. The Zengaku.com site is probably used more regularly by more Zengaku lovers than all our iOS sales combined.

However that type of calculated analysis isn't exactly what Zengaku is about and we will produce an iPad version soon. But hopefully the new features will be enough to drive a few more sales and make that effort make a bit more sense financially. We also would really like to create some other applications on the tablet, smart phone, desktop and web front that we've been rattling around for a while but have not had the time to prototype while trying to get this update complete.

But on the brighter side we've added a number of great features in this upcoming release we think you'll enjoy.

Support for multiple orientations and locking an orientation if you so desire.
A clock to time your gameplay.
A chance to brag about your time via Twitter or Facebook.
A mechanism to easily share your love of our little application with your friends and followers on either Twitter or Facebook.
A lot more puzzles to chose from including a set of Jumbled Mini Puzzles.
Jumbled Mini Puzzles where there are 6 digits still, but each puzzle could use a different 6 digits from 1-9.

We learned a lot in this release. We spent a lot of time dealing with the limitations of the Interface Builder and the dangers of integrating 3rd party libraries. We also learned about some of the difficulties in supporting devices that are still running older iOS versions. Luckily some of us have such devices so we discovered these issues in our own testing. Hopefully you'll appreciate the work we've done here and support our application with rave reviews and sharing the Zen with your friends and family. We'll keep working to make the application better as long as there are Zengaku lovers out there.

The BIG new features in version 1.2 is: MINI PUZZLES!

2010-09-26T20:31:00.000-07:00

Shortly after we released Zengaku, we realized that the puzzle game could be a bit much for a lot of people when they first looked at it. We thought hat if we provided some good help information and some hints that would be enough to get them over the initial shock of looking at that blank puzzle screen. However we soon found that these things just weren't enough.

Our review from App Safari was the last straw. It was a very positive review. And we've been very appreciative of that. The one bit of criticism they had was that the puzzles were a bit too much for the reviewer. Who even stated that they were no number puzzler and never actually finished a game. This made us sad. ;-(

So we decided at that point that our new number one feature was going to be a smaller version of the original game that would allow new players a chance to sharpen their skills a bit before taking on the challenge of larger puzzles. Our puzzle generation specialist set about tweaking things to see what we could do. So we created a number of puzzle boards that used the numbers 1-6 rather than 1-9 like the larger version do.

I'm actually not a big number puzzle fan myself. My wife is the one who usually tests out our new puzzles for me since it just isn't really my thing. But the with the mini-puzzles that changed. They didn't take me as long to work through in general. But we've got a couple of permutations that are still crazy hard. But that's good too.

I just realized we never published this post and we should have. I'm righting that wrong now.

To Redshirt or not to Redshirt?

2010-05-16T06:27:00.000-07:00

So I've been thinking about our company name the last couple days. There has been an upsurge in violence in Thailand where some protestors called the Redshirts have been causing a bit of a ruckas. The reason for the blog post is just to clear up the lineage of our name. I doubt anyone that knows us personally or who'd read this blog (since they are probably a fully overlapping ven diagram) would suspect that we knew about the other usages of Redshirt before we were formed. Although some people have politely (playfully) pointed out the overlapping name recently.

The connotation for us is directly linked to our general nerdiness. As nerds who play too much WoW and get way too excited about the next Apple product or will argue for hours about the merits of Java vs C++ or how much the use of square brackets sucks in Objective C; we obviously associated the Redshirt in our name to a small television program that started back in the 60s and attempted to take us on journey "where no man has gone before."

With that in mind we've been a bit distressed as we found out that our name, which we thought was somewhat fun and playful, is actually associated with violence, protest, even a white paramilitary group from the southern US.

So lets recap a bit shall we? Please, please, please think of us and our name with the following video in mind:

But do not think that we have anything to do with the much more serious stuff going on in this video. This is NOT at all something we are trying to associate with. (Regardless of the validity or not of the protestors problems with their government of Thailand. We just simply don't know anything about the issues at hand and what to stay out of it.)

So remember we're fun. Not serious. Just like our game we made for the iPhone and iPod Touch: Zengaku is fun and nerdy. Not serious and deadly. Ok. I feel better now that I got that off my chest.

Zengaku Lite - Marketing success?

2010-04-26T06:02:00.000-07:00

Well... it has been a few days now that we've had Zengaku Lite out there. It already has many more downloads then Zengaku, and we've had a couple of days with multiple sales of the full version.

We initially started out with the $0.99 price because we figured we would target impulse buyers and we were more concerned with numbers rather than profit. As the sales began to trail off, it became apparent that we needed to figure out marketing... and maybe people really do want to try before they buy.

With the release of Zengaku Lite - we raised the price (to $1.99) which I feel is still a steal for the quality of the game. So now users can try before they buy, and if they like it, I don't think the extra buck will be a factor.

Now if only we could find a way to get everyone with an iPhone to try Zengaku Lite. I mean... it's free! We're trying Facebook ads, and the review on AppSafari (4.5/5) has likely helped a bit too.

Zengaku 1.1 and Zengaku Lite!

2010-04-23T19:00:00.000-07:00

Before Zengaku was even released, we were already working on the next version. Here's a quick overview of what changed.

Most of the changes in the 1.1 release are internal details. We fixed a whole bunch of memory leaks, and a few minor bugs. These won't be visible to most of you, but it gives us a cleaner code base to help us with some upcoming features.

A few user visible changes you may notice are:

We now show statistics for your puzzles. From the puzzle book selection screen, you can see how many puzzles you completed, and how many are in progress.
The "Contact Us" button now presents an email form, rather than taking you to the Mail app.
There's now a link back to the Redshirt Labs website.

And the biggest feature of all, there's now a Lite version!

Zengaku Lite has the same gameplay as the original, and is Free! You get fewer puzzles, but it gives you the chance to try the game before you decide that you really really need to buy it. And you will... just try it!

Get Zengaku Lite at http://www.redshirtlabs.com/zengaku/lite or Zengaku 1.1 at http://www.redshirtlabs.com/zengaku/.

My First iPhone App is going to be HUGE!

2010-04-12T18:48:00.000-07:00

I think that when most first time app developers set out, they tell themselves "I'm just doing this for fun, but if I hit it big, woohoo!" I know that as a team, the Redshirt Labs crew felt that way. We'd love to hit the jackpot... but we also just wanted to explore, grow, and experience.

Well, if you are a first time app developer just in it for fun, I have some advice/thoughts/opinions for you:

Target Market

Before you submit your app spend at least one week thinking about who your target market is, and how you are going to reach them. Because submitting to the app store and praying doesn't work. You can tell all your friends to buy it, and that will get you a few sales, but it will quickly die out. You can drop boat loads of cash into ads... and quickly watch that money disappear with very little to show for it.

Target market is also important when you are soliciting advice on your app. People who don't own a phone that has apps on it aren't your target market. People who do own one but don't spend money on apps aren't your target market. People who do spend money on apps but don't like the genre of app you are producing aren't your target market. So you can get feedback from all these people, and much of it will be good valuable feedback. But at the end of the day you need to remember that what is important is what you target market wants. Better to have 80% of people hate your app and 20% of people think it is the best thing ever than to have 50% of people think "yeah, it was ok."

Descriptive Name

I think Zengaku may have failed us here... it sounds Japanese and looks like Sudoku but more Zen... but I'm sure 99% of the people who see it in the app store think "meh." If they clicked on it, well our description is top notch and I'm sure they'll like what they see. If they like Sudoku. So 10% of 1%. I think a name that stands out and will get the customer to investigate further is what you need.

Review Sites

I'm still undecided on these... There are lots out there, and we contacted many of them (including giving them promo codes so they could get free copies of our app). As far as I know we have 0 reviews to show for it. Many sites didn't get back to us, and others let us know that they were swamped but a few dollars would get us a review. Frankly, that might be a better way to spend the money then on ads... at least people go to review sites looking for apps to buy/try.

--Edit: We got a review!! App Safari we thank you!

Ads

Set a budget. Think about your wording. Then think some more. If you can find people in your target market, solicit their advice. You are going to be paying by the impression or by the click. Either way... it isn't enough that they click the link, you need to close the sale afterwards. Part of that depends on your description and write up sure... but a lot of it depends on who clicks on your ad. You want customers, i.e. people in your target market, to click your ad as much as possible. You want to make sure other people, who will never buy your app, do not (I guess if you are paying by impression this doesn't matter so much).

Crazy week in Apple news

2010-04-12T16:58:00.000-07:00

I've been quite enraptured in the discussions this weekend after Apple dropped a rather large bomb on Adobe's head with a change to the developer agreement that has proven to be slightly controversial. The one thing I'm not quite clear on so far is understanding exactly how they'd enforce that particular rule. But nonetheless if you do need a recap Gruber has a good post or two on the subject. And there are some passionate arguments on both sides.

Are they going to review our source code now? If not I'm not sure what an application binary would look like if it were produced with other languages other than the approved set, but ultimately compiled using the Apple tool suite. I have yet to see anyone discuss how this might be accomplished. The only thing that comes to mind is that they'd have to review our code as well. I can't see that going over very well. Maybe they have some tools that they don't want to tell us about that can sort this out. Maybe they have installed some software into every mac sold to monitor what language you use when developing your application. I dunno I really haven't got a good idea at this point.

I guess this discussion is mostly interesting to me since the our current application doesn't make use of any of these other frameworks. But we were certainly looking at those as an option at some point. Likely for other applications. Although for now we actually want to be developing in the native environment for any platforms we end up supporting so that we can build up better platform knowledge. I big part of what interested me and I think a few the other guys about doing this was the opportunity to learn these new embedded development platforms and build something fun. I'm sure that learning how to build apps with Titanium or Unity 3D, or even Flash that could run on a number of devices would be good too, but just not yet. So I'm going to be sitting back and watching where the chips fall on this one. And for now I'll keep my actual opinion on the matter to myself.

But if anyone has an inkling just how they plan to enforce 3.3.1 please let us know.

Evolution of the Zengaku Interface

2010-03-24T17:43:00.000-07:00

Developing the Zengaku UI has been an interesting experience. It has gone through several revisions, for both technical and artistic reasons. Below are some screen shots outlining the evolution of our interface.

Zengaku was my first iPhone app, and my first using Objective-C and the UIKit. It was a big learning curve. The first thing I worked on was trying to draw the actual Zengaku puzzle screen. Below is the result.

The basics are there. We have an appropriately sized grid, filled with a bunch of numbers. Of course, its horribly ugly... so the next step was to make it a bit prettier.

At first, I was using a single UIView for the grid, and drawing everything in its callback. After reading the API documentation a bit, I thought it might be a good idea to make each of the grid squares its own Core Animation layer.

I then added some numbers, and changed the colour scheme a bit. Notice that the numbers decrease in size when there are more of them in a single grid square. Also notice that the puzzle isn't actually a valid puzzle yet -- I was just randomly generating a bunch of grid squares just to test the rendering code.

Andrew and Tim worked on getting the puzzle loading working, and I was able to modify the UI to render it. Tim and I added some number buttons along the bottom of the window, and then Andrew added some actual game play logic, and below is the result. You are looking at the very first Zengaku game ever played!

You may notice that the right most column, and the bottom row do not have any consecutive bubbles. This was a bug I discovered while trying to solve this puzzle. If you look closely, you'll also see that the borders of the cells are visible inside the bubble itself. Another bug.

We then tried working on the colour scheme a bit. As you can tell, we are not artists...

Up to this stage, each grid square was its own Core Animation layer. This seemed to work fine for us, until we got our iPhone developer account. When Zengaku was running on the actual hardware, we found that the rendering was horribly slow. As in half a frame per second slow. Definitely unplayable (especially when zooming and panning).

We tracked the problem down to our overuse of Core Animation layers. I re-wrote the rendering code to once again use a single UIView, and below is the result. The performance was dramatically better.

Notice that the grid edges no longer peek through the bubbles. Also notice that there's an ugly white border around the screen. I did this because the number of cells (13) did not evenly divide into the resolution of the screen. So to avoid having some grid squares being at fractional pixel locations, I just padded the borders to make the pixels integers again.

The image below shows some more progress on the graphics front.

We finally decided to get a real artist to help us. We recruited the help of Cheyney Sadler, and the result was fantastic! Its amazing what a big diffence it has made. Thanks Cheyney!

Finally, I'll leave you with this montage of some of our other screens. I hope you'll agree that the final version turned out much better than these prototypes!

A Brief History of Zengaku...

2010-02-08T18:55:00.000-08:00

I think that the real origin for Zengaku is probably when I went to a cottage in 2000. One of the necessities on a good lazy cottage vacation is a puzzle book. The puzzle book on this particular vacation had about a hundred different types of puzzle, and I enjoyed about four of them.

My favourite type by far was the "Sum Total" puzzles. There were about 4 of them in the entire book. Much later I would find out that they were in fact Kakuro puzzles. 2000 is Ancient. Sudoku madness had not struck yet. And Kakuro was completely unheard of (even though I was playing them of course).

I don't know where I found the patience for it (I can easily get distrac) but somewhere in 2000 and 2001 I found the patience to put together my first Kakuro puzzle generator. I don't remember if the first puzzles were even playable - I was a pretty green programmer, still in school at the time. But it kept my mind working, it was programming that wasn't just fulfilling some silly useless course work, and it probably saved me from destroying my wrist playing Quake 2.

By 2003 I was pretty sure that my puzzles were the coolest thing ever and if I just put them on the web then riches and happiness would be mine. So I did what any conscientious computer engineer would do. I found free hosting, I did no marketing, and I made sure the webpage was pretty ugly. I don't think I even got a domain at the time. Obviously the overnight sensation failed to kick in. Still - SumTotalPuzzles.com was born.

In 2004, one of the Coop students employed where I was working was a math student who shared my love of puzzles. He let me know about the World Puzzle Championships, and sent me a link to their 2004 Championship warm up package. As I worked my way through it, low and behold, there was my puzzle! But wait - there was something special about this puzzle. It was a Kakuro with a Sudoku twist. Rows and Columns have each number once and only once? Consecutive numbers are indicated? The depth that these simple modifications added to the puzzle were like candy to me.

The first thing I did when I got home was I started modifying my puzzle generator to follow the same rules. It took a lot of tinkering - but eventually I had it producing nice looking puzzles - it even had a usable user interface!

Eventually I got the website looking better, and I posted a free version of the game up there, with a Paypal option to purchase a version that will literally generate 1 million different puzzles. I even made some sales. Probably about 15, maybe 20. But still, it sure felt good!

It was probably around 2006, maybe 2007 that Sum Total Puzzles became Zengaku. The origin of that is simply friends at work giving me feedback that "Sum Total Puzzles" is a terrible name. You should find something Japanese sounding. Yeah - Sudoku was in its prime around then. So I used several online translators and searches to try to figure out an appropriate Japanese sounding name for my puzzles. Zengaku is literally "The Total Sum" in Japanese. At least I hope it is... it would be pretty terrible to find out it meant something offensive at this point!
Well - a quick Google found this: EUdict translation. So not only does it mean "total, full amount, sum" but it can also mean forehead. Ha - I guess if you get a hard one that could be considered a face-palm. :-)

With the name change came more effort being put into the website. I had been generating puzzles and literally posting screen shots of them so that there was a daily puzzle on my website. I spent some time (not enough to do it well) to figure out style sheets and all that jazz to put together an interactive puzzle. And then life just kind of happened. Every once in a while I'd realize that I needed to generate more puzzles for the site (often after it went blank for a day or two or five). Sales ground to a halt and I was probably one of the least responsive webmasters of all time.

Fast forward to 2009 and I find myself working at a company with lots of smart people, who are great programmers and the iPhone invasion is in full swing. One person at my company hit it big with an app. Like quit-your-job big. I'm pretty sure that when news about that broke out, everyone who owned a Mac immediately went home and downloaded the SDK. And everyone who didn't own a Mac seriously thought about buying one.

Well, a few months went past, and no one else hit it big with an app. I don't know how many have tried. The reality was that you didn't just need to be a good programmer, you needed a good idea. And the ability to stick with something all the way to completion. It can be so easy to start programming something and then get distracted. The first couple of days are literally like you are eating manna from heaven, but it can quickly become a grind. Or at least boring enough that TV, or computer games seem like a better time investment.

So we're at work one day talking about writing apps, and how you needed motivation and commitment and a good idea. Or at least something easy to create for the first one. Well - I don't own a Mac, but I did have my puzzle website. So there we are talking about it and suddenly we are committing to each other that we are going to get this done. Together we'll have enough social pressure to actually follow through to the end. I knew that that was what I needed. Someone to kick me in the pants. Or at least make me feel guilty enough that I would stop playing games, or reading books, or watching TV and just program something to completion. Not 50% complete, or 90% complete just don't touch the big red button it'll crash, but 100% complete - rock solid.

It was probably Kevin's willpower that got us creating a partnership agreement, and getting a business number - I think the rest of us were just kind of in a daze. Regardless - we committed to each other to get it done, and I think the result is fantastic.