Large File Support for Android

Just a few days ago we announced Large File Support and Facebook Users for iOS.

We’re big believers in maintaining parity between our iOS and Android offerings. Parse makes it easy to move across platforms and our developers love us for that. Rest assured, we’re sticking to that philosophy.

So, to that end, we’re happy to announce large file support for Android!

Check out the docs and give it a try.

Stay tuned for Facebook Users in Android and let us know what you think.

Ilya Sukhar
October 28, 2011

Large File Support and Facebook Users

Today, we’ve got two awesome releases for iOS: Large File Support and Facebook Users.

Large File Support

We already support passing in NSData as attributes on a PFObject. This is handy for small bits of data, but, we don’t recommend it for large data, since that can impact download time when loading the object from our servers.

For large data, you should use our new PFFile class. Head on over to the documentation and give it a try!

With this class, you’ll be able to easily upload large files directly to Parse, and then associate it with PFObjects. The nice thing is now you can have direct control of when the client starts uploading or downloading the PFFile objects, and these events don’t need to happen in conjunction with saving the PFObject.

As an example, this is how you can save a photo as a PFFile object, then associate it with a PFObject:

NSData *imageData = UIImagePNGRepresentation(image);
PFFile *imageFile = [PFFile fileWithName:@"image.png" data:imageData];
[imageFile save];

PFObject *userPhoto = [[PFObject alloc] initWithClassName:@"UserPhoto"];
[userPhoto setObject:@"My trip to Hawaii!" forKey:@"imageName"];
[userPhoto setObject:imageFile             forKey:@"imageFile"];
[userPhoto save];

View the full documentation for large file support

Facebook Users

With Parse, it’s now a cinch to add Facebook authentication to your mobile app. We think it’s even easier than using the official Facebook SDK itself!

If you upgrade to the latest Parse SDK, it now includes a copy of the Facebook SDK. PFUser now has native support for authenticating via Facebook, which will create or log in PFUser objects automatically. Head on over to the Parse Facebook documentation to see how easy it is.

For example, this is the code to sign up or log in a Facebook user:

[PFUser logInWithFacebook:permissions block:^(PFUser *user, NSError *error) {
    if (!user) {
        NSLog(@"Uh oh. The user cancelled the Facebook login.");
    } else if (user.isNew) {
        NSLog(@"Facebook id @% signed up and logged in!", user.facebookId);
    } else {
        NSLog(@"Facebook id @% logged in!", user.facebookId);

The following happens with this code:

  • The user is shown the Facebook login dialog.
  • The user authenticates via Facebook, and your app receives a callback.
  • Our library receives the Facebook data and saves it to a PFUser. If it’s a new user based on the Facebook ID, then that user is created, if not, they are simply logged in.

What used to amount to a whole pile of server and client side code is now reduced to a few lines of Parse SDK code.

View the full documentation for Facebook integration

James Yu
October 24, 2011

Parse in the Appcelerator Marketplace

Parse adoption in the mobile development community is skyrocketing. More and more apps deploy on the Parse platform every day. As they develop their apps, mobile developers are also expanding the Parse ecosystem with various unofficial integrations, libraries, etc.

When David at Forge42 showed us his Parse module in the Appcelerator Marketplace, we were ecstatic. Many of our users are using Parse with Titanium Mobile and we’re happy to see a full fledged module to help them do so.

So, go check it out here!

We plan to highlight other community integrations in the future so keep
an eye on the blog and do let us know if you make one! As always, we welcome feedback.

Ilya Sukhar
October 19, 2011

Introducing Our Future Pricing

Here at Parse, we know it’s important for all app developers to understand what their costs are as they develop on a platform. To that end, we’ve gotten a lot of questions about what our pricing will be once we come out of beta.

I’m happy to announce that today, we’ve published our future pricing structure. The plans are usage based. Here they are published here for convenience:

Data Objects: up to 50,000
API Requests: up to 200,000 per month
Push Notifications: up to 1,000,000 per month

Data Objects: up to 100,000
API Requests: up to 400,000 per month
Push Notifications: up to 2,000,000 per month

Data Objects: up to 600,000
API Requests: up to 2,500,000 per month
Push Notifications: Unlimited

Data Objects: up to 2,000,000
API Requests: up to 7,000,000 per month
Push Notifications: Unlimited

If you’re an enterprise expecting large volumes, contact us for customized pricing.

Please note that Parse is entirely free to use during our beta. The above pricing will only come into effect when we come out of beta.

As always, let us know what you think.

James Yu
October 5, 2011

Parse is now compatible with ARC

This week the talk of the town in the world of mobile app development is, of course, the iPhone event tomorrow.

The release of iOS 5 is imminent and with that comes a big change: the introduction of Automatic Reference Counting (ARC).

So, in anticipation, we’re happy to announce that Parse is now fully compatible with ARC and ready to be included in projects using the latest SDK. In the process we’ve also made it much easier to get up and running using Parse. The Parse framework is now packaged as a .framework bundle compiled universally for both iOS devices and simulators.

If you’re upgrading from an older version of Parse we recommend that you
take a look at the Quickstart Guide again after downloading the new version. It’ll walk you through the slightly tweaked installation process as well as the new method of setting your Application ID and Client Key.

For those of you interested in learning more about ARC and its intricacies, here are a couple great resources:

As always, let us know what you think.

Ilya Sukhar
October 3, 2011



RSS Feed Follow us Like us