Ben,
I agree with you about the crying need. From a product roadmap point
of view, this is a really obvious value for many developers. But I
wouldn't jump to a solution too quickly. I've been thinking about the
problem for a few days now and my opinion is that initial load data
should come from
On Sun, Aug 1, 2010 at 11:59 AM, Bret Foreman bret.fore...@gmail.com wrote:
I'm going to investigate the option of using Amazon S3. There exists a
Java library for S3 access along with methods to access all the AWS
services: http://aws.amazon.com/sdkforjava/
The question remains, if I just use
On 8/1/2010 11:59 AM, Bret Foreman wrote:
Ben,
I agree with you about the crying need. From a product roadmap point
of view, this is a really obvious value for many developers. But I
wouldn't jump to a solution too quickly. I've been thinking about the
problem for a few days now and my opinion
Now that wireless companies are moving to metered data plans, I would be
very annoyed if I found that the initial install of an app required a
network connection to download an undetermined amount of data. If anyone
does this, they should make sure that they tell the user how much data
is
Yeah, I thought about that. The two app solution is certainly clunky,
though, especially when it's such a common problem. I think an S3
connection would be easier to implement, and certainly easier for the
user.
I've seen several dictionary apps that include the data in an app that
you
5 matches
Mail list logo
