QuickBooks Online on iPhone - my impression

After I have setup my Quickbooks Online, I tried to access it via my iPhone (https://accounting.quickbooks.com/m) as stated in the System Requirement from my previous post. 

My initial impression of the iPhone web app was good and with high expectation, but end up with disappointment as this is only a very basic read-only app. In my mind that this is a iPhone web app, not a native app, which means you must be online to access this app, and also means that you are accessing the live database at that time. I can't add or modify any of the master (bank, customer, vendor, employee), and transaction records (Who Owes Me, Who I Owe). I can understand the synchronization issues of the native app, but I cannot understand why these basic features are missing from the web app.

At least one thing meet my expectation, i.e. when tap on the customer phone number, it prompted whether I want to make a call to the number or not.

Looking forward to a more usable version of QuickBooks Online for iPhone.

App Store for Composite Business Application

I like to see iPhone as the application container with some basic modules/functions (the embedded apps like MobileMail, MobileSafari), and apps in the iTunes App Store are like additional modules/functions that can be added to the application container to form a composite application that is tailor-made for that particular user.

The Ubikwiti and U-KwikShop were developed based on the same principle, i.e. the 

Ubikwiti is the application container running within the Definition-based Dynamic Engine (DDE) framework, and the additional business components (modules/functions) can be added to the application from the U-KwikShop (App Store) any time to tailor make the business application for that particular user or business. 

Similar to iPhone, each of the components are independent from each other, but as Ubikwiti is a platform for business application, we have built in a set of common business objects such as Account, Party, Contact, Document, Journal, etc as the building blocks (like LEGO blocks) to 'snap' the components together. For example, a customer record created in Customer component can be used in the Invoice component as both using the same Party business object.

This gives the user the real power to build his/her own composite business application, or the real on-demand application. Anyone can start with some basic components to build a personal finance management application, and grow it to an order-to-cash financial application, or even to a fully function accounting system, just by adding more components from the U-KwikShop.

Another benefits of this approach is on the update of the components. It is similar to apps in iPhone, user can update the components individually, or even skip some updates if they are not relevant. User makes the decision.

I can see that the power of Ubikwiti application can be enormous once the U-KwikShop starts to have a lot of business components that link up with 3rd party web services such as online collaboration services, banking, payment, tracking, and so on.