We are developing an Android application that should be notified on individual cell phone basis (each cell phone receives unique push notification based on cell phone registration id). Part of notification procedure should be collecting cell phone IDs (we have them stored in our database and the application that will generate the push notification has the registration id) and we need help making sure they get formatted properly and sent though our self hosted bt server back to the app. thanks in advance Jeff

The BuzzTouch push service does not have your desired granularity. It will do a push to ALL devices that has the app. For your situation, explore Parse's service. They have channels for discreet targeting of users. I know of one guy who assigns a single person to a channel. Of course, depending upon your quantity of devices, and the amount of notifications, Parse might be expensive. Have you explored a "call home" capability that would pull the notifications, rather than push the notifications? -- Niraj

this would be a problem for us since we have thousands of users. wow - it really looks like we have wasted a lot of time on the wrong technology. I have messages out here from a month ago where people told me I could do what I wanted - sending different push notifs to different people using buzztouch. bummer

re: http://www.buzztouch.com/forum/thread.php?fid=AB0C5B863CFC9CA3FF2711D&tid=AB0C5B863CFC9CA3FF2711D

re: http://www.buzztouch.com/forum/thread.php?fid=AB0C5B863CFC9CA3FF2711D&tid=AB0C5B863CFC9CA3FF2711D

Looks like you are just posting a link to this thread buddy.

Bear in mind that the BuzzTouch framework may still be the correct one as your foundation as it meets the majority of the requirements. One always has to supplement any framework by filling in the gaps with outside SDKs, Libraries and Custom code. Your Push Notifications requirements is quite extreme. Not matter the implementation (BuzzTouch or otherwise), you would still have to roll your own or bring in another SDK, such as Parse or Amazon or PushWhoosh. You are a savvy developer. Before the Push Notifications came onto the scene, how would you have solved your requirement? By thinking about this in a different context, I am certain one or two solutions will emerge that build upon the BT Foundation. Finally -- Consulting and development work is available from within. Start with David Book and branch out from there. Don't be shy. Let us know what you've decided. I'm curious to see how this one gets solved. :-) -- Niraj

You had asked the same question about 1-month ago. http://www.buzztouch.com/forum/thread.php?tid=93FD1C1AEF383FC43E98BE3 My response at the time is similar to today's response to you. You have not been deceived. Perhaps you had misunderstood my cautions to you back then. I have seen warnings that Apple can throttle the Push Notifications if they are coming fast and heavy. However, I have not heard of that actually happening. I bet Google will be of the same mindset. Perhaps you might be the first to battle-test them? I am interested in helping, you are not being abandoned. :-) -- Niraj

@Niraj- I continue to see posts that refer to the built in BT push service like it is a working model but have yet to find anyone who has actually got it working properly? Are you saying that you have successfully implemented push in a BTv3 Self Hosted environment?

@rob - what you're going to find out is that a lot of this stuff does not work at all as advertised. Take the login screen for andoid - it does not work and we had to dig into the code to get it to work, which was very disappointing, especially since we made the assumption starting out that these plugins did work. that problem aside - my question is this. If Buzztouch can 'really' (and we don't believe it at this point based on all the disappointments thus far and a healthy level of skepticism) send push notifications in it's 'native' state - HOW does it know WHO to send them too - if it can only send to 'all instances' of the app - that list of 'all instances' must be maintained somewhere?? - in it's database and if we can dig into that code then 'WE' can figure out how to NOT send to 'all instances' and only send to one specific person based on the content of the message we give BT to send. Jeff

@Jeff, I don't disagree with your comments, but if you are self hosted, you can view a list of all registered devices and only send to specific devices(that is if you can get Push to actually work). And those devices are listed in your device table in your self hosted MySQL server. BUT the real problem I have is that I have seen dozens of posts on here by other users directing people to use BT Push, but I have yet to find even one user who has actually gotten it to work. I have no problem with it not working (things break and need to be debugged) my problem is that I continue to see posts everyday from veteran BT users directing new users to use BT Built in Push yet they cannot provide any proof that they themselves have gotten it to work.

@rob - the developer who helped us out - Dusko has apps working and our app is almost functional - so at a basic level it does work.

@rob - we're going to know in the nest few days about push since we're ready to dig into it or use parse - just don't know yet.

intresting, you have it working on a Self Hosted BTv3 app? From your previous posts I though you were using the web based BT Server

we have multiple linux boxes in a data center so self hosting is easy for us.

we have multiple linux boxes in a data center so self hosting is easy for us.

Yea. I can't get BT push to work either. Android, self hosted.

@Patrick -- please ensure your host allows the Ports for Push Notifications GoDaddy is bad HostGator is good