I've added notifications to my PWA app and i'm facing a question I can't find an answer. Is there a way to hide the source of the notification? (the line between the title and the body, saying where the notification came from)? Thanks!
Browser vendors don't let developers remove site information from notifications for security and auditing purposes. They want to ensure that if a bad site is abusing notifications, users can easily identify the site and block them.
Related
I am working on a custom webApp for Microsoft Teams, I would like to manipulate the badge notification for my App (btw I am not sure if it's the right name), I need to add a counter like teams does for new messages or another symbol to indicate different actions in my app.
Is there a way to do this? using a sdk, api, (#microsoft/teams-js, etc...)
Thanks
Currently we don't have any API to display notification when some action happens in an app. You can raise an UserVoice for this if this needs to be considered as a feature request. If you want to Send activity feed notifications to users in Microsoft Teams please go through this documentation.
I found this post on getting Notified when a file changes on dropbox. The problem is that the "/delta" API endpoint requires polling. I want instead to subscribe to events about file changes.
Ideally, I could subscribe to both "new file" and "file updated" events for a specific folder. I could then give dropbox a URL pointing to my own app that would be called when those events occurred. This is similar to how Twilio works. You can provide a URL to be POSTed to whenever your phone number receives a text message, and then your app can respond to POSTs to that URL however it wants. This seems like a much more elegant solution than polling -- is there any way to do it with the dropbox API?
UPDATE 6/5/2014
We actually have webhooks now: https://www.dropbox.com/developers/webhooks
(original reply below)
No, Dropbox doesn't support this.
BTW, the general term for the sort of notification you describe is a "webhook."
http://developers.box.com/webhooks/
it seems like Box API has webhook. You may want to try it.
I received an email today regarding Dropbox WebHooks that is in the beta phase:
If you're interested in helping us out, just click through to fill out
your information, and we'll be in touch:
https://dropboxapi.wufoo.com/forms/dropbox-webhooks-api-beta-feedback-contact-info
Happy Dropboxing!
Dropbox now offers webhooks, although not with a event_type filter
https://www.dropbox.com/developers/blog/90/announcing-dropbox-webhooks
I was redirected here by Shopify support. I have three main questions for a project I'll be working on and wanted to see how possible some of the things would be.
We are looking to develop a plugin for use with Shopify to track purchases through the use of a link shortener (to see which link referred what purchases, etc.). I have a few questions that I'm not 100% sure on even after reading through the documentation.
The first problem that I seem to have is tracking the query string that the link shortener appends to the URL once it redirects. For this service, they use "?visit_id={hash}" and I need to be able to access this--at the very least on the "Thank You" page after an order. I saw in the docs that there is "landing_page_ref" (http://wiki.shopify.com/Order#landing_site_ref) but considering our query string is "visit_id" instead of one of the acceptable parameters, how would I be able to use that query string?
Lastly, I just have a question about how webhooks work with plugins that are on the app store. I know I can just call webhooks to wherever I want, like my personal server, but if this app gets onto the app store, I obviously don't want to hook everything to my own server. Is there a way to make it run on the store itself, and which URL should I use?
Lastly, what is the preferred method for handling configuration options for the plugin? Is there a way to hook into the admin backend or would all configuration have to be in a file within the plugin?
Thanks,
Andrew
I'll do my best to answer these for you. It sounds like you're used to building plugins for something like Wordpress - Shopify apps are a bit different.
You can't access anything on the thank you page for the order.
The thank you page/checkout process goes through a secured Shopify page that you don't have access to - so if you want information about what your URL shortener attached to the store pages, you'll need to retrieve it while they're on the page (using something like a ScriptTag + Javascript to track the query string), or hope that it's inside the Order when you retrieve it later (using the API or a webhook).
Webhooks need to talk to a server you run.
They send the information to you, and then you process it and deal with it. If you want to use webhooks, you will need to run a server with your app on it for the webhooks to talk to.
You manage your own config.
Because you're running your own server to handle those webhooks, you handle configuration for your plugin there. The apps I've worked on typically have their own database for managing configuration options, as well as an admin panel to manage them (it's what the user accesses when they click 'Log Into [Your App]' on the "Manage Apps" screen).
You'll need to run your own server to host your Shopify app.
I work on Google Chrome extension for facebook.
I have a button and if you click on it, a popup with latest active threads appears. I want to say to facebook server that no threads are 'unseen' afterwards. So that the messages jewel on Facebook main page will show no notifications.
Can I do this with Graph API? POST calls to graph.facebook.com/thread_id with unseen=0 don't work.
Alternatives?
You do not have write access to the inbox. Only read access read_mailbox. Sorry, but that's the only permission that Facebook currently has available. See: https://developers.facebook.com/docs/reference/api/permissions/
However, you can keep track of the inbox items on a remote server's data store and have your plugin query that to know what's been "seen". So at least from your plugin's perspective, things are showing up correctly.
This is a problem that every developer will face when building their apps: how to contact the reviewer of your app to notify them of an update, new release, help topics, etc?
Some things I am thinking:
Include an RSS feed in your app which you can update to notify the users of the app.
Include a twitter feed regarding your app. How to go about this?
Include a way for the users to subscribe to a mailing list. This way, I can send a mass-email to the users who opted-in? Any suggestions here?
Any other ways that you think this can/should be done? Any existing solutions you can point me to will be great. Thanks in advance.
One way, for contacting a specific user who created a review of an application is to go to Zune Social (at http://social.zune.net/home) and create a new message. You can then enter the Zune Tag of the user who created a review.
Personally, I'd try to do all three - have a web page/site, with an RSS feed, and a subscription link (so they can subscribe to the RSS feed via email) and then post any updates to your twitter account as well.
You can't really force a user to do any of these, but having the options available, and linked from inside your app on the about page is probably good practise.
You could also include some kind of "Update Available" feature inside the application. Try to make this as unobtrusive as possible obviously. Obviously if they've still got the app installed they'll get an update notification from the marketplace anyway.
Sam
Besides the suggestions made by samjudson, I'll also recommend having a support-page with a direct option to send a email to you. Here's a example of a support-page from one of my applications. I've received lot of emails with suggestions for improvements, or complains about bugs. And since it's by email, it gives you the option to respond directly to people.
Another thing about reviews. Don't take them to serious. Most people only rate negatively (since humans like to complain), and by such a lot of reviews are often misinformed, outdated, or the users just been plain ignorant.