IGG Developers' Blog

Archive for the ‘iOS’ Category

No Name, But We Got Game

Saturday, January 7th, 2012

Even if we don’t yet have a name for it, development of iBank for iPad has been on going for over a year now. In an earlier post I talked about some of the design decisions and metaphors used for iBank for iPad. There is one in particular that is relevant to the short tour I’m about to give of iBank for iPad:

You can think of it as having your own personal financial report  on your iPad. If you sat down with a financial planner who asked a series of comprehensive questions to get a handle on your finances, what you would walk away with would be like our iPad app — your complete financial picture, always up-to-date.

The screenshots you are about to see are not polished and not final. Some still contain debugging code and some have pretty poor formatting, so please ignore this for now. For this post I want to offer of a broad overview; future posts will delve into specifics of its functionality.

So without further ado, here is one of the first screens you’ll see in iBank for iPad.

 

In this screen you can see we’ve embraced a “portfolio on a desk” metaphor. Each portfolio is an iBank document, and so yes: this app will support multiple documents (unlike iBank Mobile). A swipe gesture lets you browse the documents, the + button creates a new one, and the trash icon deletes the centered document. When you press the + button, you are taken to a modal “assistant” that walks you through document setup. Tapping one of the leather bound portfolios opens it to reveal the “document home screen”:

 

The Document Home Screen is the heads-up display (HUD) for your financial life. Everything you wanted to know is here. The idea is that you are looking at a financial report that is on “magical paper” — with binding on top (which conveniently acts as a toolbar). The paper can expand in size to accommodate users with lots of accounts and it responds to various touch gestures including dynamic interactions. At the top of the page you’ll notice there are two boxes: summary information for all classes of finances, and to the right of that, your upcoming bills and notifications. You’ll also see that all of your accounts are listed and grouped into general categories: “Bank Accounts,” “Investments,” “Mortgages and Loans,” etc.

Touching the various elements causes a new sheet of paper to slide in from the right. For example, if you tap “Credit Card” the new “sheet of paper” that slides in shows the details for that account:

 

Although it isn’t evident in this screenshot, the selection on the bar chart drives the transaction list below. So if you wanted to see transactions from September to November you would select that range in the chart. To edit a transaction, you simply tap it, and to get back to the Document Home View, you just swipe the page to the right to make it go away. (You can ignore the debugging info at the top of the page — as I said, these screens aren’t polished.)

From the Document Home Screen, if you select an investment account a new piece of paper slides in, but we customize what is displayed to emphasize the investments in the account.

Notice on this screen the Positions table (but ignore that temporary green color used in the bars). Here you have an overview of how each of your investments is doing. Tapping a position slides in a new sheet showing additional details of the specified security along with a list of all transactions associated with the security in the account.

So that is a brief overview of iBank for iPad. I haven’t shown all of the screens as I want to save some goodies for the next post. But this should give you a pretty good sense of how this app will work and how to navigate through it.

-Ian

iBank for iPad: First Thoughts

Wednesday, November 16th, 2011

We’ve been getting lots of requests and comments about our forthcoming iBank for iPad app. I wish I were here to show screenshots and give a release date, but I’m not. However, I am here to talk about some features it will have, and what our guiding strategy has been during the development process.

First, I want to say we are not simply porting our iPhone app to the iPad. While that would have certainly been the easier route, we don’t think that is what our users want (and as one of those users, I certainly want something for more than quick entry and checking account balances). I should also say that we are not porting our Mac product to the iPad. The iPad is its own beast. It’s mobile, but not as mobile as the iPhone; its screen provides for a lot more data to be shown. And of course, it has the touch screen. Some of the best iPad apps are ones where the device becomes the app’s real-world metaphorical cousin, like Apple’s Calendar app — which feels like you are interacting with a desktop calendar. Similarly, using Contacts is like using an address book. Not all apps have such straightforward translations to what they might represent in “real life” (take the Settings app, App Store or FaceTime apps, for example).

So what will iBank for iPad be like? You can think of it as having your own personal financial report or portfolio on your iPad. If you sat down with a financial planner who asked a series of comprehensive questions to get a handle on your finances, what you would walk away with would be like our iPad app — your complete financial picture, always up-to-date.

In designing the app, there has consistently been one overriding theme: simplicity for the user. I want to make a distinction here when I say, “simplicity”. I don’t mean this is a simple app for tracking a cash account. The app is powerful, not only under the hood, but also from a practical standpoint; for example, you will be able to see and edit all investment transactions. By simplicity I mean ease of use. There is no “Download” button — you just launch the app and your accounts are updated. No import window will appear where you need to help decide which transactions to commit to the account. Instead, new unreconciled transactions just appear and they are conveniently marked “new.” The Get Quotes button is gone too; again, the market value of your investments just updates.

I think it’s also fair to talk about what the app won’t have. It won’t run on iOS 4 or earlier. There will not be bill pay. I know some of you will be upset about this… I’m sorry. At some point I would like to do another post about why we haven’t brought bill pay to our products. (Hint: it isn’t for technical reasons.)

I look forward to writing in more detail about iBank for the iPad.

-Ian

We have been invisibly busy

Wednesday, September 28th, 2011

People have been asking for some news about iBank for Mac. Let’s first start with what we’ve accomplished, albeit quietly, and then we can talk a little about what is still to come. iBank 4, which we released one year ago, was our most successful product launch, and the press and feedback on it have been overwhelmingly positive. Since that time we have released 11 updates, fixed over 119 bugs and implemented about 32 user-requested features. Yet since we launched iBank 4 the world has changed in three ways that we had to respond to but did not see coming.

First, the Mac App Store. It was clear as soon as Apple announced the Mac App Store that people would want to get our software from it. The store has some real benefit to customers and we wanted to be a part of it. However, there were some non-trivial code changes that needed to be made to support the store.

Second, Lion. Everyone knew Lion was coming but until WWDC (in June of this year) we did not really know how big a change Lion really was. Our customers expected that our software would work on Lion. The truth of the matter was that iBank as it existed in June would not run in some edge cases once Lion shipped in July. So we had to do some non-trivial changes under the hood to make iBank Lion-compatible. One of the challenges we faced was that iBank 4 shipped supporting 10.5 and that we did not want to drop those customers’ systems in order to support Lion (Lion’s development tools do not allow building 10.5 PowerPC apps). This work continues with iBank 4.3, which will have its first Lion-only feature: full-screen mode. Next we’ll work to implement sandboxing, a major security change which only affects things behind the scenes.

The third is the death of MobileMe and the birth of iCloud. As many of you know, we use MobileMe as a syncing platform for iBank for Mac and iBank Mobile. We need to replace this with some other solution. It might be iCloud, but we are still evaluating the best way to sync our products. Certainly iCloud plays a role but we are not ready to commit to what that is.

Our latest update to iBank is 4.3, which will be released in the next few days or so. In addition to integration with iBank Investor, iBank 4.3 a number of bugs that our users have been requesting we address. We will continue to fix bugs and add refinements and we will certainly need to make further significant changes to decide how to gracefully terminate MobileMe syncing with iBank Mobile.

So that is a lot of what we have been doing with iBank. Now let’s talk about how iBank improves in the future.

The two new products that we have been talking about on the blog, iBank Investor and iBank for iPad, both can help shed light on this. Much of the work being done in those products will result in new features in iBank for Mac. This is because we build all of our products on a set of shared code. Right now if I count the files in iBank for iPad, 80% of them are shared or planned to be shared with iBank for Mac. In fact, the best thing about working on the iBank for iPad project is that we actually get to implement a number of features and enhancements that will later make it into the next iBank for Mac release. You can think of iBank 4 as running on our “CoreFinance” 1.0 engine and iBank for iPad will run on CoreFinance 2 and a future version of iBank will run on it as well.

We have a binary of iBank for iPad that loads on iOS 5 and you can see accounts. Some of the UI is starting to take a more final look. But there are still many significant components that need to be implemented. I wish I had some screenshots of iBank for iPad, but we aren’t ready to share that part of our progress, yet.

Thanks,
James