ok Guys, yet another thing what might catch your interest in this article. Yep: it is official now on the parse blog. I also got this mail:
Last edited by a moderator:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS bye bye PARSE?
- Thread starter grandM
- Start date
- Sort by reaction score
lol I can be fast now and then
I've always been cautious about relying on others people's work. This hit me as a surprise though. I am truly lucky I did not integrate parse. I considered it but decided to go CoreData, and later on CloudKit. Imagine all those developers worldwide having apps running on parse. I'm glad you were only at first base with your OS X app.
[doublepost=1454024343][/doublepost]
Maybe it will be easy to set up their code on a server?
This is kinda strange, why would this be a problem if they are going open source? Isn't setting up a server pretty easy now?
I don't have much background on this, but is there anything that Parse does that you can't to with CloudKit?
It seems that they are just taking down their own servers, which actually seems strange by itself. Given that others are going big on Cloud, you'd think FB would be right there in the middle of it.
I don't have much background on this, but is there anything that Parse does that you can't to with CloudKit?
It seems that they are just taking down their own servers, which actually seems strange by itself. Given that others are going big on Cloud, you'd think FB would be right there in the middle of it.
Well I imagine Android has some API that addresses that, but that does make the code less transportable.
Wouldn't be surprised it someone came out with a more universal solution.
Parse does a ton more. Most importantly, it's multi-platform. In addition to cloud stuff, it handles user accounts, analytics, push notifications. You can run tasks/scripts that fire off events on their servers (like "check this website every 15 minutes for an update, if something changes, send a push notification to these people"). Parse is fantastic for what it does. I have a single Parse "app" that all of my iOS apps use. That way I can keep a single login across all apps. I'm surprised Facebook is killing it.
Same here on the surprised part. With all the push going into cloud type services, it's hard to understand FB's logic on this move.
The upside is that they'll be going open source, so for most a small RaspberryPi could maybe do the job with a simple internet connection. IDK what it takes to run a Parse type server, but at least they're going open source. Hopefully it'll be the full system. Maybe some companies will jump in and take things over, but IDK if it's really a money making model for all the low usage apps.
My sentiments exactly - I'm not too sure that space is worth investing into.
But then again, it's a proven product that had a wide audience range and could make decent revenue, so I bet there are others who will try to emulate it as close as possible.
Looks like Amazon has most of what Parse did covered under their AWS Mobile Hub:
https://aws.amazon.com/mobile/
https://aws.amazon.com/mobile/
Could be but you face a lock-in once more. This incident has proven the risks once more.
Yet another reason you should always build your own backend. It takes a little more work but in the end it is definitely worth it. Not to mention the fact that cross skilled developers make more $$$ lol.
Personally I prefer building my own backends simply so that I can do most of the logic on the backend. Things like querying the database should really never be done on the app.
I think Parse encouraged a lot of developers to pick up some pretty bad habits so over all this is probably a good thing.
Personally I prefer building my own backends simply so that I can do most of the logic on the backend. Things like querying the database should really never be done on the app.
I think Parse encouraged a lot of developers to pick up some pretty bad habits so over all this is probably a good thing.
Some HUGE name apps and games use(d) Parse. In many, many instances it's a giant waste of time and money to roll your own backend (why reinvent the wheel?). So if "you should always build your own backend," by that logic, don't have your backend hosted remotely either. You should build your own server and self host it, that way you don't have to worry about a remote host's potential downtime or upgrading software versions that will break what you wrote. As for your point about querying, etc, Parse allows you do do all of that on the backend if you want with hosted code. I'm curious what kind of bad habits you think Parse encouraged?
The Parse library is going open source. So you have two options:
1) Find another library.
2) Use Parse library on a server, either hosted or your own.
But either way, all of your Parse commands will work if you redirect Parse to your server instead of their main servers. And honestly, Parse was too much of a crutch for people who were using it as a means of claiming they knew how to integrate web based data services into their app.
Knowing Parse != knowing JSON query, post/get commands and server communications.
Knowing Parse == knowing how to use a sandbox library that does all the grunt work for you.
Learn AFNetworking, build your own JSON queries and you'll be a lot more powerful as a developer. And if you really like Parse, just host it when it's open source.
The fact that it's going Open Source means it's just a matter of time before someone adopts it into a GitHub repository and CocoaPod.
1) Find another library.
2) Use Parse library on a server, either hosted or your own.
But either way, all of your Parse commands will work if you redirect Parse to your server instead of their main servers. And honestly, Parse was too much of a crutch for people who were using it as a means of claiming they knew how to integrate web based data services into their app.
Knowing Parse != knowing JSON query, post/get commands and server communications.
Knowing Parse == knowing how to use a sandbox library that does all the grunt work for you.
Learn AFNetworking, build your own JSON queries and you'll be a lot more powerful as a developer. And if you really like Parse, just host it when it's open source.
The fact that it's going Open Source means it's just a matter of time before someone adopts it into a GitHub repository and CocoaPod.
I read a case study about a developer that used AWS and the costs went thru the roof. They ended up leasing their own server and saved a HUGE amount of money. I understand that Amazon is cashing in on AWS/Cloud services.
I'd think of this just like a database server. You can pay thru the nose, or use some open source system. The high end systems costs vs learning or paying a programmer to roll one for you.
Parse had a free level and there are TONS of apps out there that could scrape by on a free ride. FB makes nothing on them. No ads, no nothing.
FB itself is nothing new. It's a BBS/message board. It's not much different than the millions of discussion boards just like this one. The only difference is how it's structured and how popular it is. That's how FB get it's value, they run the worlds biggest message board.
The Parse business model doesn't make money at the lower end. It's free and if they charged for the light users, they'd find something else.
Just like FB itself, who'd pay for FB? Few if any. It's been tried, people want free. FB and Parse lived because of being free or free for most. Once you charge, people look for best value. It's not that hard to make a server, open source it and every gets it for free/near free.
Parse was more of a public service for most.
Watch someone come out with a $50 RaspberryPi server that does the same thing.
I'd think of this just like a database server. You can pay thru the nose, or use some open source system. The high end systems costs vs learning or paying a programmer to roll one for you.
Parse had a free level and there are TONS of apps out there that could scrape by on a free ride. FB makes nothing on them. No ads, no nothing.
FB itself is nothing new. It's a BBS/message board. It's not much different than the millions of discussion boards just like this one. The only difference is how it's structured and how popular it is. That's how FB get it's value, they run the worlds biggest message board.
The Parse business model doesn't make money at the lower end. It's free and if they charged for the light users, they'd find something else.
Just like FB itself, who'd pay for FB? Few if any. It's been tried, people want free. FB and Parse lived because of being free or free for most. Once you charge, people look for best value. It's not that hard to make a server, open source it and every gets it for free/near free.
Parse was more of a public service for most.
Watch someone come out with a $50 RaspberryPi server that does the same thing.