Push Delivery

[bagusflyer]

It's very sad that parse.com will terminate within one year. Some of our applications will be affected. I'm developing an application right now which is using parse.com as backend. Should I re-develop everything or I can just use parse-server in my own server with current source code?

Another question is regarding with push notification. A few of my applications are using Push Notification. Are you going to release the source code for this part in the future? Or we have to develop our own Push Notification system?

Thanks.

[gfosco]

We'd like to see a push delivery system added to parse-server, whether the community writes it or we do... It's definitely going to happen.

I can't make the decision for you, but I think with parse-server and the open SDKs, you can continue building on Parse for years to come (just host the server code yourself.)..

Over the weekend I setup Mongo and parse-server on a $5/month DigitalOcean box to build a quick idea, it was super easy.

[pfcvik]

It would be very grateful about that tutorial

[inlined]

@bagusflyer I'm the former tech lead for Parse Push and now work on Firebase/Google Cloud. I'm keen to see that few to none of my former customers get left out in the cold for having put their faith in my product. If you want to go into detail on your use cases, I can try to help you evaluate some migration paths too. My best expertise would be using AWS (what we built Parse on) and Cloud (what I now work with).

FWIW, Parse Push had much more complicated requirements back in the day. Both Apple and Google have improved their push protocols dramatically, so a new service might be easier to build.

[gfosco]

Developing a push delivery system on parse-server will not be a difficult process. Luckily, it will only need to support a single app, instead of hundreds of thousands of apps.

[prodigga]

@inlined @gfosco thanks for responding to questions and being so open about all this.

I recently (a month ago) recommended to my boss that we use Parse as our backend for our mobile games leaderboards and async 'tournament' gameplay mode. Parse was an awesome choice - it let us get started quickly and let us do lots of cool stuff, like checking to see if your new score beat a friends score and sending that friend a push notification if it did - all with cloud code!

I think the push notifications are a big part of any 'connected' app and it would be great to see a parse push implementation, or at the very least a tutorial/guide to migrate existing device instalations form our parse database to a 3rd party service.

Also, are developing in Unity3D and, unfortunately, Unity3D related features usually get lower priority. I don't see this being much of an issue, since most of these changes are back end stuff. But a few things did catch my eye when skimming over the migration guide - it mentioned in the guide that we should release an update to our app and make sure the app points to the correct server. I'm not even sure if this part of the API is exposed for the Unity version of the Parse client, for example.

I am rambling here, and just voicing concearns, I guess what I am trying to figure out is if we really would be able to transfer seamlessly across to private hosting (minus push notifications) using the Unity version of Parse.

[richardjrossiii]

@prodigga Correct, migration for Unity 3D is still in limbo. It's there for the rest of our .NET SDK, but I still need to write the glue code to make ParseInitializeBehavior accept a URL.

Rest assured it is coming, along with a few other Unity features that have been in the pipe for a while now.

If you wouldn't mind opening an issue for that on the actual .NET SDK repo (https://github.com/parseplatform/parse-sdk-dotNet/issues), we can handle the actual discussion of that there.

[prodigga]

@richardjrossiii Opened an issue here parse-community/Parse-SDK-dotNET#166

[prodigga]

@gfosco could you go in to some more detail as to how one would go about implementing this? It sounds like you know how you would go about implementing it already, so your insight would be great for other developers.

[yemaw]

Will Parse team going to actively maintain and develop Parse Server and Parse SDKs after 2017? This is very important for us to make decision whether we should change to another service or host Parse Server our-self.

[zhouhao27]

@yemaw, I have the same concerns as you have. If Parse SDK will not be actively maintain then we have no point to continue to use it in the future. Maybe we'll take some efforts to migrate to other system or to build our own backend system if that is the case. But I feel the painless solution could be to host Parse Server on our own server.

[bmueller]

@gfosco would really appreciate a push delivery system added to parse-server in the near future. I make heavy use of the subscription channels, so having something provided by your team would make this transition a lot less painful.

[chavanshashank]

Yeah push delivery is important!