In App Purchases vs 2 Applications
<p>I've been doing some reading up on In App Purchases.  My 1st Android App i released had 2 separate versions: a "Lite" version and a "Pro" version.  I've found keeping 2 apps a bit of a hassle, and thought In App Purchases could be a better way of doing things.</p>

<p>However, in most the sample code I see, it seems to imply there is a connection and service required, and the possibility of dealing with non-trivial situations like service disconnections. (<a href="http://developer.android.com/google/play/billing/billing_integrate.html#billing-download" rel="nofollow">http://developer.android.com/google/play/billing/billing_integrate.html#billing-download</a>)
e.g.</p>

<pre><code>Bundle ownedItems = mService.getPurchases(3, getPackageName(), "inapp", null);

public void onServiceDisconnected(ComponentName name) {
   mService = null;
}
</code></pre>

<p>Concerns I have with IAP are 
1. how the application knows you've purchased an "upgrade" when offline: Do you'd actually need an internet connection to verify a purchase of the upgrade has occurred in the past, or has the got that information cached and hence would work fine in an offline mode.
2. Does it have any major performance impact on apps calling it which would make a dedicated pro app a preferred solution.
3. Is it more complex or buggy on certain phones?</p>

<p>So in general, based on the above concerns and the fact that I want a simple app, where 1 purchase unlocks more functionality - are IAP's the right tool for the job or should one stick to Pro vs Lite, 2 applications</p>
