ANDROID: APK & OBB expansion management

Something you want to see in a LiveCode product? Want a new forum set up for a specific topic? Talk about it here.

Moderators: Klaus, FourthWorld, heatherlaine, robinmiller, kevinmiller

Post Reply
rmuzzini
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 60
Joined: Mon Oct 08, 2012 11:30 am

ANDROID: APK & OBB expansion management

Post by rmuzzini » Mon Feb 23, 2015 5:03 pm

hi.
am i the only one making big apps here, where "big" stands for "larger than 50 MB"?
i hope not.
as probably all of you know, android apps to be published on google store can't be larger than 50 MB. for bigger apps, google lets developers to load in the store as many expansion packs as needed (2 GB max size each), hosted by G for free.

http://developer.android.com/google/pla ... files.html

it would be very nice if LC took care of this limitation, giving us a help while compiling the android app.
this way, for example:

1.
while compiling, by segmenting the app in 1 main .apk file and as many .obb (or simple zip) files as needed (that's the way twixl publisher does, for example)

2.
coding side: by introducing a new specialFolder path to allow developers to recall the assets in code

<shared-storage>/Android/obb/<package-name>/
<shared-storage> is the path to the shared storage space, available from getExternalStorageDirectory()

3.
browsing side: by teaching the engine how to read from .obb files (as LC already does, after all, an apk beeing nothing but a zipped archive: see LC dictionary for "specialFolderPath": "An Android application is installed on the phone in the form of its zip package. This means that any assets that are included are not available as discrete files in the native filesystem. In order to manage this the engine essentially 'virtualizes' the asset files you include, allowing (read-only) manipulation with all the standard LiveCode file and folder handling syntax. To access the assets you have included within your application, use filenames relative to specialFolderPath ("engine")")

it would be a very big help for developers, in my opinion.

and easy to implement, or i'm totally wrong?

ludo
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 66
Joined: Mon Dec 03, 2007 6:10 pm

Re: ANDROID: APK & OBB expansion management

Post by ludo » Sat May 09, 2015 3:46 pm

Any news ?
[...]
I filled a request on the LiveCode Quality Control Center with your post (my english is too bad !)
http://quality.runrev.com/show_bug.cgi?id=15346

istech
Posts: 130
Joined: Thu Sep 19, 2013 10:08 am

Re: ANDROID: APK & OBB expansion management

Post by istech » Mon Jun 15, 2015 11:56 am

Yes you are right about this limitation and it would be good to implement. In the mean time my workaround for this was to a have a server and download the content I needed separately rather than using the OBB expansion.

ToddFabacher
Posts: 280
Joined: Fri Jan 09, 2015 6:15 pm

Re: ANDROID: APK & OBB expansion management

Post by ToddFabacher » Mon Jul 13, 2015 9:55 pm

Count me in...We had to also do a full Web Service just because LC can't send a 50 MB database on Android. This is not difficult to program.

--Todd

Post Reply

Return to “Feature Requests”