The summer has been really busy and we’ve dusted off the JS SDK, stripping out large parts of its legacy.
Backbone style callbacks are definitely out.
You’ll find this post in your
_posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run
jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.
To add new posts, simply add a file in the
_posts directory that follows the convention
YYYY-MM-DD-name-of-post.ext and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works.
As we previously shared, the Parse service is shutting down at the end of this month. Specifically, we will disable the Parse service on Monday, January 30, 2017. Throughout the day we will be disabling the Parse API on an app-by-app basis. When your app is disabled, you will not be able to access the data browser or export any data, and your applications will no longer be able to access the Parse API.
The holidays are upon us! Thanksgiving has come and gone, and Christmas is coming up in just three and a half weeks. This leaves app developers little time to enjoy a stress-free app update.
New versions of iOS and Android OS are now widely available. Here are some suggestions to think about as you update your application.
With the upcoming Parse.com shutdown just 150 days away, we’d like to take some time to talk about the things we have been doing to get ready on our side.
The ability to send push notifications from the Parse Dashboard has been requested by many of you. Powerful targeting, content building and rich options for sending pushes to your users is one of the pillars of Parse, and the ease of use of Parse Push is one of the things that makes Parse great. Now, we are bringing that ease of use to the Open Source Parse Server and Parse Dashboard, running on your own infrastructure. If you’ve configured push already, all you need to do is update your version of the Parse Server and Parse Dashboard and you can start sending pushes.
One of the key concepts behind Parse is the Query, which lets you tell the server which objects you need. The Query is based on a “pull” model. Every time you want to get new data, you run another query. For some applications, like realtime games or messaging systems, it’s more convenient if you can get a constant stream of object updates.
With the winding down of the Parse hosted service and the transition to the Open Source Parse Server, many of you have been asking how you will manage your app when it’s running on your own system. Today we are answering that question with Parse Dashboard. You can start using it today to manage the apps that you have already moved to Parse Server, your apps that are still on Parse.com, and your apps that are still in development and running on Parse Server on your development machine. You can even manage them all from the same dashboard.
In this post, I will attempt to convince you that Parse Server is worthy of your time and interest, even if you’ve never heard of Parse before. I will also make the case that Parse Server is and can be objectively better than the hosted Parse service. I hope that by the end of it, you will consider evaluating it for your next project.