heyooohhh… thankyou
honestly I’ve been busy on another project so I really wasn’t paying attention till the other guy posted. But that is great news. I put together an app with c2dm awhile ago as a workaround, but it was a crappy way to do things…
steve [import]uid: 55582 topic_id: 31525 reply_id: 130363[/import]
Thanks for the thorough feedback, much appreciated. Hope there won’t be any more delays now. [import]uid: 21746 topic_id: 31525 reply_id: 130493[/import]
Thanks for the thorough feedback, much appreciated. Hope there won’t be any more delays now. [import]uid: 21746 topic_id: 31525 reply_id: 130493[/import]
Hi, are you still on track - will this be available before or in the beginning of next week?
Thanks! [import]uid: 21746 topic_id: 31525 reply_id: 130788[/import]
Hi, are you still on track - will this be available before or in the beginning of next week?
Thanks! [import]uid: 21746 topic_id: 31525 reply_id: 130788[/import]
read todays blog post… it sure sounds like no, more like not anytime soon
[import]uid: 55582 topic_id: 31525 reply_id: 130825[/import]
read todays blog post… it sure sounds like no, more like not anytime soon
[import]uid: 55582 topic_id: 31525 reply_id: 130825[/import]
Anyone want to let us know what the delay is on android push notification?? [import]uid: 89018 topic_id: 31525 reply_id: 134489[/import]
High priority bugs/issues take priority over features. For example, we’re currently getting a lot of reports that Google Play in-app purchase no longer works correctly. Probably something has changed on Google Play’s end that we have to now support, because in-app purchases on Android used to work brilliantly. We have to work on this issue this week.
That said, we did implement “custom” data support to local/scheduled notifications on Android as of last week’s daily build. This was a crucial piece that is absolutely needed by push notifications, or else you would have no means of identifying what the push notification was for. [import]uid: 32256 topic_id: 31525 reply_id: 134528[/import]
Yet another bullshit answer from the masters of excuses.
According to an e-mail I got from you a month ago, you were done with it, but could not release it before the new public Corona release was live. Your build servers started producing daily builds again a week ago, so it should have been out then. Thats exactly what you wrote to me. Has it happened? No. [import]uid: 21746 topic_id: 31525 reply_id: 134599[/import]
I’ve never said Push Notifications was done. The e-mail response you received, which was from comment #29 up above, clearly states that we were “planning” on getting it done by the next daily build. We didn’t achieve that date unfortunately because we had to take care of some high priority bugs/issues that many of our customers have encountered. All we had time for was to add “custom” table support for notifications. Again, issues that affect the majority of our customers will alway take priority over upcoming features.
That said, posting rude responses here on our forums is not going to score you any points with anyone. Especially with me. It comes across as unprofessional and immature. Ultimately, it achieves nothing. If you need push notification or any other feature “now” and you can’t wait for us to implement it, then your options are the following:
Honestly, I won’t take it personally if you or anyone else has to use another tool to achieve your goals. I understand that you have your own commitments and deadlines that you have to achieve, because I too know what it’s like when a library or SDK that I’m using has limitations that I can’t live with. Again, getting upset online achieves nothing.
That said, we know we’re unable to keep up with all of the demands being sent our way. We’re simply receiving more demands than we have the time and resources to handle; which also indicates that our customer base has significantly grown and we need to grow with it. This is why we now provide an Enterprise version of Corona so that our customers can add features that Corona does not provide support for. This is also why we are adding a native plugin/add-on framework so that features can be implemented by 3rd parties, which we’ll be rolling out very soon. This way, we can focus on core features and supporting as many Android/iOS devices and OS versions as possible, which is what we do best and is our main focus.
In any case, that’s my 2 cents.
We’ll have time to work on push notifications again next week. [import]uid: 32256 topic_id: 31525 reply_id: 134686[/import]
Anyone want to let us know what the delay is on android push notification?? [import]uid: 89018 topic_id: 31525 reply_id: 134489[/import]
High priority bugs/issues take priority over features. For example, we’re currently getting a lot of reports that Google Play in-app purchase no longer works correctly. Probably something has changed on Google Play’s end that we have to now support, because in-app purchases on Android used to work brilliantly. We have to work on this issue this week.
That said, we did implement “custom” data support to local/scheduled notifications on Android as of last week’s daily build. This was a crucial piece that is absolutely needed by push notifications, or else you would have no means of identifying what the push notification was for. [import]uid: 32256 topic_id: 31525 reply_id: 134528[/import]
hola,
so is this native plugin/add-on only going to be available to enterprise users?
( i haven’t cursed you out online )
Steve [import]uid: 55582 topic_id: 31525 reply_id: 134840[/import]
Yet another bullshit answer from the masters of excuses.
According to an e-mail I got from you a month ago, you were done with it, but could not release it before the new public Corona release was live. Your build servers started producing daily builds again a week ago, so it should have been out then. Thats exactly what you wrote to me. Has it happened? No. [import]uid: 21746 topic_id: 31525 reply_id: 134599[/import]
Steve,
The following blog post formally announces our upcoming plugin feature…
http://www.coronalabs.com/blog/2012/12/11/what-is-project-gluon/
Plugins will be made available to all Corona developers. That is, you do not need Corona Enterprise to use a plugin. However, you do need Corona Enterprise to create your own plugins, which makes sense since you need to write them in native code using Xcode and the Android SDK.
We actually have a working plugin framework now. We’re already working with some key partners to evaluate and to see how easy it is to develop a plugin now. This includes Amazon. It’s quite exciting really. This means that you no longer have to wait for us to implement features… or wait for us to update a feature when breaking changes occur in a feature. The breaking changes in SDKs or online services is what’s really killing us right now because we can’t predict when they’ll happen and it forces us to stop what we’re currently working on. If we can get the SDK/service provider to write the plugin, then it’ll be their responsibility to update it when they make breaking changes. Should make things a lot smoother for everyone. [import]uid: 32256 topic_id: 31525 reply_id: 134869[/import]
okdokey…
would there be any restrictions to the selling of the plugins to other developers… are you guys going to implement some sort of marketplace for the sale of third party plugins? No one is going to spend a grand to hand out the plugins for free…
[import]uid: 55582 topic_id: 31525 reply_id: 134873[/import]
We haven’t fully figured out how we’re going to distribute plugins yet. We do plan on distributing some free plugins on our end. Particularly for popular plugins/features. We’re definitely open to the idea of hosting 3rd party plugins. But we think it might also be a good idea to have 3rd parties distribute their own plugins as well so that we won’t have to be the middleman from a business or tech-support standpoint. Regarding non-free plugins hosted by us, I’m not sure what our stance is on that yet. I’m sure the head honchos over here are open to that idea as well, but at the moment, we’re more focused in getting the initial wave of 3rd party plugins made available to everyone first.
If you’d like to send us your ideas, then by all means post to our current blog post here…
http://www.coronalabs.com/blog/2012/12/11/what-is-project-gluon/
Or send them privately to us here…
http://www.coronalabs.com/about/contact/
[import]uid: 32256 topic_id: 31525 reply_id: 134885[/import]
I’ve never said Push Notifications was done. The e-mail response you received, which was from comment #29 up above, clearly states that we were “planning” on getting it done by the next daily build. We didn’t achieve that date unfortunately because we had to take care of some high priority bugs/issues that many of our customers have encountered. All we had time for was to add “custom” table support for notifications. Again, issues that affect the majority of our customers will alway take priority over upcoming features.
That said, posting rude responses here on our forums is not going to score you any points with anyone. Especially with me. It comes across as unprofessional and immature. Ultimately, it achieves nothing. If you need push notification or any other feature “now” and you can’t wait for us to implement it, then your options are the following:
Honestly, I won’t take it personally if you or anyone else has to use another tool to achieve your goals. I understand that you have your own commitments and deadlines that you have to achieve, because I too know what it’s like when a library or SDK that I’m using has limitations that I can’t live with. Again, getting upset online achieves nothing.
That said, we know we’re unable to keep up with all of the demands being sent our way. We’re simply receiving more demands than we have the time and resources to handle; which also indicates that our customer base has significantly grown and we need to grow with it. This is why we now provide an Enterprise version of Corona so that our customers can add features that Corona does not provide support for. This is also why we are adding a native plugin/add-on framework so that features can be implemented by 3rd parties, which we’ll be rolling out very soon. This way, we can focus on core features and supporting as many Android/iOS devices and OS versions as possible, which is what we do best and is our main focus.
In any case, that’s my 2 cents.
We’ll have time to work on push notifications again next week. [import]uid: 32256 topic_id: 31525 reply_id: 134686[/import]
Any updates on this? Getting push notifications working is a big deal to all of us. We have to compete with other apps that use them. And just to be clear: Corona Labs works for us. We are the ones that pay you, we are your clients, and you need to focus on what matters to us. If your answer is for us to shut up or go use another SDK then Corona will soon be a thing of the past. [import]uid: 94309 topic_id: 31525 reply_id: 135083[/import]