Sidebar doesn't appear on mobile. It should have a toggle behavior.

As discussed here, there is a stub api you can run locally to simulate interaction with the appboy API.

As we saw with the minification bug #14 , some issues are only exposed when interacting with the real api. It would be a great improvement to add a smoke test suite that starts up the stub-api server on the CI machine and runs tests against it.

Most of the Ember apps my team is responsible for currently use the location: 'hash' option and the production versions of these apps are hosted in subdirectories, so a typical URL would be in the format "https://www.example.com/foo/bar/index/html#/baz".

For various reasons external to this issue, some of our internal links cannot be specified as Ember {{link-to}} calls and instead have to be hardcoded, as in <a href="...">. One of the implications of the location: 'hash' setting is that these href values have to be specified as hash fragments, i.e. "#/baz" instead of "/baz", in order to work properly.

For consistency for our team, we would like to be able to have Braze modal buttons be able to support URLs in the hash-fragment format. This is not possible with the current implementation of getAppRoute, which simply uses the pathname from the parsed URI, which in the case of the example above will simply be the user's current (pre-hash) URL.

The workaround is of course to not use the '#' character in the Braze link targets in this scenario. However I believe this is a useful enhancement that (if implemented correctly) should not impede other uses.

I am working on a potential fix and will submit as a PR shortly.

#I don't currently use this feature - is there anything we need to do to integrate this into the Ember ecosystem?

https://www.appboy.com/documentation/Web/#news-feed

There are a few methods in the appboy library that take anonymous functions as callbacks:

• isPushGranted(yesCallback, noCallback, safariWebsitePushId)
• registerAppboyPushMessages(successCallback, deniedCallback, safariWebsitePushId)
• submitFeedback(replyToEmail, message, isReportingABug, successCallback, errorCallback)

To better integrate these with Ember, we should expose methods that bind to the Ember run loop and return an RSVP promise. For instance:

// addon/utils/promisified-methods.js

export function rsvpIsPushGranted(safariPushId) {
   ... logic ...
   ... returns a promise ...
}

You can pass enableLogging: true to the initialize call to get debug logging. This could be a useful feature.

enableLogging - Set to true to enable logging by default. Note that this will cause Appboy to log to the
javascript console, which is visible to all users! You should probably remove this or provide an alternate
logger with appboy.setLogger() before you release your page to production.

https://js.appboycdn.com/web-sdk/latest/doc/module-appboy.html#.initialize

Right now, I assume that if the URI you're transition to is within the same hostname, it is a valid route in your ember app. However, it's possible that your ember app does not span the whole boundary of your hostname.

It would be nice if we could somehow ask the router if it recognizes a URI path and only wire up our soft transition logic in this case.