Within those, the most common page was presented first, and power user features were available one level down.
Two-level hierarchy - Features were reorganized into four major sections - Settings, Messages, Users, Delivery. You can read more about the process I used in my IA post When to Add Hierarchy, and about the redesign in the announcement post OneSignal has a fresh new UI.Īfter a few iterations, the solution I settled on included the following changes: I built out the information architecture before jumping into visual design. I tackled this problem by planning forward a few versions to features we wanted to build, organizing current and planned features into similar clusters, finding opportunities to simplify workflows by taking an opinionated approach, and identifying shared actions and desire paths. Original dashboard (left) and redesign draft (right)
ONE SIGNAL WEB PUSH INTERNNT EXPLORER SERIES
Management activities (market analysis, Series A deck/pitch, financial models, refined customer support flows, etc).
Conducting user research (data analysis & convos) and writing case studies.Rewrite & rearchitecting of OneSignal documentation.Design & launch of email support and audience segmenting tool.Design & launch of self-service Web Push flow, part of our web push product in use on ~3% of top 100k internet sites.Redesign of core OneSignal Dashboard including design system, custom form elements, and information architecture.I joined as the 6th person at OneSignal, and during my time I was the sole PM and designer responsible for the product experience. OneSignal.OneSignal is the largest push notification and marketing automation service, sending 8+ billion daily notifications on 1+ billion devices for 1.2mm+ developers. I am not sure if the error getting logged is the expected behavior (didn't notice it before) and it is stopping from the listener getting triggered.Īlso, I am thinking that changing the URL might have been a coincidence because I did not test for the click actions 1 week before and 2 days after changing the URL. I can see the same error logged into the console upon clicking on the notification. Nothing that I tried seems to resolve the issue.įinally, I have checked another website that uses One Signal web push. I have created a small test angular 6 application (to make sure that the app isn't creating the problem), integrated with one signal and deployed it in another server(to see if the server or the IIS is the cause) with a different URL (not the 2 that I used before).ĭeleted the cache and cookies as well before trying any new change. I have also tried by creating a new app in One Signal and changing the configurations on both the front end and one signal settings. I have tried changing the one signal settings: disables the site is not fully HTTPS toggle and then uploaded the OneSignalSDKWorker.js and OneSignalUpdaterWorker.js, manifest.json to the root directory and they are accessible without any redirects on the respective URLs where they have to be. The native versions of the mobile apps (Android (Kotlin) and iOS (Swift)) work perfectly fine before and after the change in URL. I am getting the same error across all the browsers. OneSignal.push(['addListenerForNotificationOpened', function (data)
0 kommentar(er)
