zulip-mobile

e up, something happened, fetch a notification." Apple likely doesn't do anything with the notification text, but it's a given Google datamines the hell out of it. They also still don't have any form of e2ee. Here's another five year old ticket requesting end to end encrypted chat, where a bunch of people say "here's a long list of apps that support e2ee" and Zulip devs go "gosh golly how do they handle keys? Math is hard." https://github.com/zulip/zulip/issues/6096

service pages linked from the app contained the zulip.com website footer, which in turn link to the pricing page for Zulip's paid offerings. This means our Privacy Policy could be a way to get people to buy something without paying the Apple tax! We "resolved" this, on the advice of their appeals expert, by passing a special parameter when loading these pages from the ToS/Privacy links in the mobile apps that hides the header/footer sections of the page :(. * In May, Apple reviewers repeatedly rejected the Zulip mobile app for linking to its own source on GitHub. At first we thought the problem was that we had recently set up GitHub Sponsors [1]. Further correspondence determined that the problem was even more ridiculous: Any GitHub page has a tiny link in the https://github.com/zulip/zulip-mobile footer for GitHub's own pricing! We were able to convince them to approve it in the end, but we were close to giving up and removing the GitHub links. I'm still upset about the whole experience because it was a huge waste of energy. It's not clear to me whether these rejections are what Apple's policies intended or just the policies being incorrectly applied. But it doesn't really matter: these appeal processes are opaque and scary and mostly consist of them repeating what you need to change with minimal explanation. If not for the entrenched monopoly, we'd be looking to switch to another vendor that wasn't so sloppy about something that's very important to us. I think the harm caused by sloppiness on the part of monopolies doesn't get enough attention. [1] This would have been wrong too, though I do know some companies use a Patreon as the way to sell their product, and I can imagine that being a workaround that Apple would be on the lookout for. But it's easy to check that we're definitely not playing that game.

nt spend time on learning specifics next-js routing. Instead I went with https://github.com/jaredpalmer/razzle which supports React Router for routing, which I use Android/react-native and React-native-web, uniformly. React-router, is also very good and useful library with nice, intuitive architecture for routing. At the end, I decided for my need the Server Side rendering is a later-stage item. So I have not spend more time on it. I suspect Spectrum did not loose much traffic because their app is not using SSA routes. Zulip chat app (may be they are spectrum's competitor, not sure) - uses React Native for mobile (https://github.com/zulip/zulip-mobile ), but something else for web. As a reference.