Getting Started with Android Bitcasa SDK

[Andrew]

Hi,

I just started with Bitcasa today, by downloading the Android sample code and starting on the REST documentation.

We are considering two options:

A) Our Android app connects to the user's Bitcasa Personal account to display thumbnails of and play their videos.

B) We use Bitcasa as the white-label cloud storage and require users to create new Bitcasa Platform accounts.

I'm thoroughly confused by what's offered and would appreciate some guidance.

1) There are 2 SDKs on GitHub: bitcasa-sdk-android, and bitcasa-cloudfs-sdk-android. What is the difference?

2) I've created a Platform account and a test user, but cannot login to the Bitcasa app in Google Play with that. Logging in with a personal account works. Is that expected? If so, how is (B) tested then?

3) What is the easiest way with one of those SDKs to input my client ID and secret and authenticate to a test user?

I've tried changing CLIENT_ID and CLIENT_SECRET in bitcasa-sdk-android MainActivity.java, and the constants in bitcasa-cloudfs-sdk-android TestAccount.java.

Thanks in advance,

~Andrew

[Davita Strong]

Hi Andrew,

Thanks for reaching out to us.

Both of your options are great ways to utilize CloudFS. If you're looking for a white-label offer, check out our Turn-key Drive solution and if you want discuss this further, please feel free to reach out to me directly at: dav...@bitcasa.com.

Sorry to hear that there is some confusion around the SDKs. 

As you've noticed there are two different Android and iOS SDKs on Github. Please use the -cloudfs- SDKs. Prior to the release of CloudFS we offered a v1 API, which a majority of the SDKs on git are for. The v1 API was geared towards integrating third party apps with Bitcasa whereas CloudFS (v2) is also geared towards integrating third-party apps - without having to lose our brand or identity.

The platform test user account login won't work with our consumer apps as they are apart of a completely different database. You'll need to create an access token with the test user and utilize the appropriate API to test with your app. Please reference our documentation to get started with CloudFS.

As for the easiest way authenticate a test user, you'll need to provide the following fields with the information found on your account page:

• CLIENT_ID
• CLIENT_SECRET
• USER
• PW
• ENDPOINT

If you're still having issues or have additional questions, just let me know.

Thanks!

[Andrew]

Hi Davita,

Thanks for your advice. I hadn't been able to connect to the native Bitcasa app through bitcasa-sdk-android (Client not recognized), but it sounds like that SDK is deprecated.

With the bitcasa-cloudfs-sdk-android, changing the values in TestAccount.java (i.e. CLIENT_ID, CLIENT_SECRET, etc.) works for me. I can upload files to the test account.

Thanks for your help!

~Andrew

P.S. My company is already discussing white-label options with Bitcasa. This is just the first time engineering has gotten involved :)

[Davita Strong]

Hey Andrew!

Glad to hear that everything worked out with the CloudFS SDK. 

If you have any additional questions, please don't hesitate to ask.

Thanks!