OneSignal Blog

OneSignal | California, New York, Pennsylvania, Texas, Utah, Washington | Onsite or Remote (Within these states) | Full Time | https://onesignal.com/careers Tech stack includes Go, Rust, Ruby on Rails, Kafka, Postgres, Redis, InfluxDB, Typescript, React OneSignal is building the best platform for businesses to intelligently engage with customers across every channel. We provide a simple interface to push notifications, email, and in-app messages, letting content creators focus on quality user engagement instead of complex implementation. We're hiring Senior Software Engineers for our Product, SDK, and Backend teams. More information and apply at https://onesignal.com/careers

Check out OneSignal (https://onesignal.com/)! We offer SMS both as a standalone service as well as part of our omni-channel offering. We offer both a seamless experience for both developers and marketers with a clean, robust API and a fully featured dashboard. Indeed we have templates for SMS that your team can share and edit without you getting involved. We have quite a lot more than that as well, e.g. see our Journeys product. Feel free to reach out to me directly for questions or feedback!

I am curious how this compares to an older YC company OneSignal. https://onesignal.com ... Sounds quite similar on the surface. Does YC bet on multiple companies in the same space?

I'm in a similar situation. Currently looking at OneSignal (https://onesignal.com/). Definitely open to other suggestions if anyone has any.

I just created an account on OneSignal: https://onesignal.com/

OneSignal | Full-Time | Software Engineers | Remote US (TX, CA, NY), UK | https://onesignal.com/ OneSignal has grown rapidly to where we are today serving billions of HTTP requests daily and sending upwards of over 10 billion messages daily. Our massive scale, small team, kindness in all our interactions, and focus on ownership and personal growth make OneSignal a uniquely great place to work. OneSignal’s vision is to power the world’s messages. Our customer engagement platform enables our users to compose and send messages via mobile push, web push, in-app, SMS and email. Engineering Manager, Remote CA - https://jobs.lever.co/onesignal/95cdf3d6-9950-4b7f-bfa6-a968da6cebcc?l… Engineering Manager, Remote NY - https://jobs.lever.co/onesignal/89071a7d-e743-461d-9849-cf5f2b0f66a2?l… Engineering Manager, Remote TX - https://jobs.lever.co/onesignal/e5bf56f7-b8be-4f00-baf1-e7908679ae74?l… Staff Product Engineer, Remote CA - https://jobs.lever.co/onesignal/20f05dc1-7b81-460d-a1a1-b8014b5986f6?l… Staff Product Engineer, Remote NY - https://jobs.lever.co/onesignal/dc39657b-69cb-4517-b110-769e0499df2d?l… Senior Product Engineer, Remote CA - https://jobs.lever.co/onesignal/fe93c2c0-e3bd-42ed-b317-1160ce7c9092?l… Senior Product Engineer, Remote TX - https://jobs.lever.co/onesignal/bc2733f1-98e4-4a66-baba-ec724aba0fdc?l… Senior Infra Engineer, Remote NY …

> Even if Chrome had push notification on iOS I can't think of any logical reason to build a push notification inside Chrome if I were Facebook Facebook has already implemented this. It is in use today on mobile web. If Safari on iOS (which powers "Chrome" on iOS) is updated to support the Push API tomorrow it will start working. Facebook has already implemented it. As for the rest we're not even talking about web at all. Back to your original post: > The web (html documents fetched via http requests) were not built with mobile devices in mind, especially websockets. In the mobile era, all messaging is based on push notifications which must go through the device vendor (APNS or GCM), and trying to support the legacy tech in this landscape is just not worth it. "Legacy tech" isn't necessary to support push notifications on web. Yes, Safari on iOS is woefully outdated for now (which again is what powers "Chrome" on iOS). But it is currently supported on Android (across multiple browsers), soon Windows, and it's possible Safari on iOS will add support in the future https://onesignal.com/blog/when-will-web-push-be-supported-in-ios/ Facebook is already using this today.

We do not sell user data. Period. You’ll sell it if you sell your company (as per your privacy policy).[1] We may disclose or transfer your personal information in connection with, or during negotiations of, any acquisition of our business, financing or similar transaction. If you wouldn’t sell it, period, then I’d suggest amending your privacy policy to include irrevocable deletion of customer data at the point your company is sold to a buyer. [1] https://onesignal.com/privacy_policy

> All major Web browsers on Android and iOS provide push notifications to websites No browsers on iOS allow push notifications on websites. https://onesignal.com/blog/the-state-of-ios-web-push-in-2020/

Web Push on Safari on iOS (works fine on desktop) https://onesignal.com/blog/the-state-of-ios-web-push-in-2020/ Safari on iOS deletes LocalStorage after 7 days of inactivity (https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-mor…

Its certainly growing. For such a young language, its being thrown at projects that would have required c/c++ previously. here's one notable one https://onesignal.com/blog/rust-at-onesignal/

See also this post about notifications delivery interruptions on Android and how to fix it: https://onesignal.com/blog/manufacturers-interfere-with-reliable-notif…

This site isn’t very well known, even to Rust people. Here’s an open Rust job right now: https://facebook.com/careers/jobs/a0I1H00000LCTYYUA5/ There’s even a Rust job open on the front page of HN right now: https://news.ycombinator.com/item?id=16767515 (specifically this one https://onesignal.com/careers#senior_backend)

Can it generate interactive graphs like the one on https://onesignal.com/blog/rust-at-onesignal/ ?

From https://onesignal.com/about: It's free; how does OneSignal make money? We make money by using the data we aggregate to improve web and mobile experiences. We also offer custom solutions to enterprise clients.

If you haven't heard criticisms of Rust, you haven't heard very much of Rust. If you give it more than a superficial glance, you will find that there are issues with Rust - build times, build artifact sizes, ability to integrate with non-cargo build systems, cross-platform compatibility, difficulty in finding developers proficient in Rust, time to train engineers new to Rust, FFI with C++ not being good and on and on. Even the very article we're discussing is by a person who is unhappy with the FFI experience and wants to improve it to unlock contributions to Linux. What makes people excited about Rust is not that it's perfect right now, nor do people claim that it's perfect. They're excited because they've seen a lot of progress in the last 3 years and see a clear path for it to become better in the next 3. Almost every blog post I've read mentions shortcomings. Take one I read today from way back in 2017 (showing that people criticising Rust is not new) - https://onesignal.com/blog/rust-at-onesignal/. While they are very happy with their choice, they mention 1. Build times being very long. This is partly the fault of rustc generating verbose LLVM IR and partly because of code-gen macros like the ones used by serde (the crate that makes json parsing easy) 2. Libraries such as async clients for postgres and redis not being available. Http clients being immature and having to spend time improving them. 3. IDE experience being poor. Of course, 2.5 years later many of…

OneSignal | DevOps, Systems, Full-Stack | San Mateo, CA | ONSITE OneSignal provides a simple interface to push notifications, letting content creators focus on quality user engagement instead of complex implementation. Our goal is to democratize push communication for everyone from individual blogs to top tier apps. We are looking for talented software engineers from any background. Our stack includes Rust, Ruby on Rails, React.js, PostgreSQL, and Redis. Experience with our specific tech is not required; we are simply looking for talented people with a big appetite for learning and shipping quality code. Specific roles and benefits can be seen on our careers page: https://onesignal.com/careers. To apply, please send your application to [email protected]. Interested in how we leverage Rust for our application? Check out this blog post! https://onesignal.com/blog/rust-at-onesignal/