I don't find any thing about the costs to make Push notifications to my iPhone app.
I want to send Push Notifications to my App, but I don't find anything about the Price.
What does it cost to send Push Notifications?
If you have your own server, you can do it for free. Depending on the language you use, there are good libraries available. With JVM languages, you can use JavaPNS, for example.
It is also possible to use an external company that specializes in this. I have found UrbanAirship is good for my needs and has a free usage tier (I have no association with them).
Bottom Line: If you use external suppliers prices will vary, and you will either find them on their website, or by asking. Apple does not charge you anything. Doing it yourself is free.
Related
I know asking this question here is not proper, I feel sorry for that.
I have tried searching websites, Amazon and Alibaba, but fail to find any product can support Eddystone-EID.
So, I think developers in stack overflow may know any product can support Eddystone-EID.
Could you share any any information for that?
The two vendors below claim to sell beacons compatible with Eddystone-EID as of October 2021:
Gimbal
Estimote Location Beacons
Before you buy anything beware that Google shut down their beacon platform web services in April 2021. I wrote a full blog post to explain what this means: Eddystone is Dead, Long Live Eddystone!
Using these web services is completely optional for Eddystone-UID and Eddystone-URL, but critical for Eddystone-EID, because the beacon identifier rotates with a crypto algorithm and a “trusted resolver” server is needed to convert the advertised “ephemeral identifier” from jibberish to something meaningful and useful.
Without Google’s beacon platform web services, I am aware of no commercially available trusted resolver for Eddystone-EID. You would need to build your own, which is a non-trivial effort. Without a trusted resolver Eddystone-EID is worthless.
Because of this, make sure the vendors above still support using their products with Eddystone-EID. In time, it is likely they will remove support in their beacon firmware.
Finally, it is important to note that just because Google gave up on their beacon web services, most apps that use Eddystone, iBeacon and Altbeacon are unaffected. Beacons are standardized and will work forever — just don’t use Google web services! Again, beacon technology aside from Eddystone-EID has no need for Google web services.
I want to create a realtime stock alert app where users can subscribe to specific stock instrument with target price. Once that target price hit, The subscribed user will be notified over the app.
A good example of such platform is Tradingview.com
For stock API's I will be receiving realtime stock quotes from My API vendor over.
As far my knowledge is concern, I'm looking at this app as Web socket OR MQTT pub/sub platform where users can subscribe to that specific instrument topic and get notified once stock price is hit.
But my knowledge is limited when it comes to thousands of users subscribing to thousands of alerts.
What technologies must be going at the backend for such kind of apps ? What must be the data flow ?
Bit late answer to this, I was working on something similar with all custom NodeJS server and instruments you want to subscribe on. It is very simple server and you can find it here https://github.com/markosole/yahoo-node-streamer
I am working on desktop App built on top of Electron which is used for subscribing to instruments, monitoring multiple instruments and creating visual and sound alerts for every instrument individually. I have not release Electron app source to the public yet.
Creating mobile app will be harder as it would require backround data and best bet would be using Flutter and Google Firestore to send alerts. Well this is very top level.. I will eventually make flutter app and share it on Github
Overlooking the fact that there are literally thousands of apps out there that do all of this already....
Your best bet might be to do one of two things:
1) Just send out the stock price and let the client app figure out the alert, or
2) Have a back-end system that just sends out the alert to the specific customer when their price point is reached.
Option 1 is something that MQTT could easily do. Option 2 could be done using MQTT, but its something of an overkill IMHO. MQTT is built for applications where one node is publishing data, and many nodes are subscribing to that data -- hence Option 1 is more in line with what MQTT was built for.
I would like to be able to make apps for clients via Heroku, but I would love it if they could sign up for the billing themselves so I wouldn't have to keep charging them monthly. Creating a team or a collaboration allows me to change the dyno type to whatever I want, charging them an arbitrary amount of money. I was wondering if there's any way to set things up where the person I'm developing for pays the bill, but has full control over what that bill will be, while I can still work on the app. A collaborator setup is almost what I want—you're not allowed to provision payed addons—but for some reason they still allow you to change the dyno type.
Also, I'm not 100% sure if this is the best exchange to be posting this on, please feel free to point me in the right direction.
There are plenty of companies out there offering texting to your landline without affecting voice service (ie zipwhip, heywire), but does anybody know what they're using? Twilio almost offers this, but it's currently in beta and only for toll free numbers. TextUs.biz has an explanation of how they do it in their faq, which explains that they have some sort of agreement with their SMS gateway provider that lets them get texts to a particular number routed to them, but afer a lot of googling I still can't find any resources on how to make it work.
(Disclaimer: I'm the VP of Engineering # HeyWire) The TextUs FAQ is spot on. SMS routing and voice routing are completely separate. OTT text carriers like us have agreements with SMS aggregators and have to abide by industry rules and guidelines. The agreements and rules may vary depending on whether you're doing short code, non-toll-free long code, and toll-free long code. International and MMS are also other dimensions as well.
In general, our application stacks connect to SMS gateways, which connect to SMSCs at our aggregator partners. Beyond that, the details of how everything works isn't technically complicated. Some the real special sauce comes in the details of all the agreements and partnerships required to get things up and running. Unfortunately, those types of details fall under the umbrella of "trade secrets". Partly due to providers not wanting to reveal too much to competitors and partly due to the agreements themselves, which prohibit disclosure of details.
Are you asking because you're trying to build something or just to try to find out some general information?
EDIT: And I just realized I wasn't logged into my account when I posted this. Oh well.
I was wondering if it is possible to develop a text messaging kind of application similar to WhatsApp, but for between WP7 devices? What difficulty programming skill level am I looking at and what would be required to develop such an app? Thanks!
In general I don't think it will be really difficult to build an app like WhatsApp. (Although I only heard about the funcationality) So I will give you the information I think you should have at a minimum.
In the first place you need your WP7 app, which I think should have push notifications to notify users about new messages. (Note: push notifications work in batches, so there will be no instant delivery notification to the end user.) You should have a login system in your WP7 app, which makes users uniquely identifiable.
Somewhere you should have a central datastore where you can store users, messages, relations between messages (replies, forwards, etc.) (Note: If your app becomes as big as WhatsApp you should have a really good scalable datastore.).
I would use WCF to communicate between your datastore and the WP7 app. Probably I have overseen something right now, but this will give you a start for defining your applications architecture.
UPDATE 12:54
As i saw your comment about where to start I searched for some documentation:
There is a free e-book from Charles Petzold which covers alot:
http://www.charlespetzold.com/phone/
Also there are a lot of code samples and documentation on MSDN:
Main overview of WP7 development:
http://msdn.microsoft.com/en-us/library/ff402535(v=vs.92).aspx
WP7 code samples:
http://msdn.microsoft.com/en-us/library/ff431744(v=vs.92).aspx
You can have a look at the Sockets Support section, which may help you to get started.