macOS: Chrome/Firefox support — would you use it?
I’m the maker of Open Links in Apps — currently a Safari extension for iOS & macOS that opens supported links in native apps and cleans messy URLs (tracking params, redirect wrappers, short links, AMP). Supporting Chrome/Edge/Brave and Firefox on macOS would mean separate extensions + ongoing maintenance, so I want to validate demand first. Quick reply (just copy one line): Browser: Safari /...
How do you prefer controlling redirects: per-site rules, profiles, or quick modes?
Redirects are powerful, so control matters. Right now the extension focuses on: per-site “Never Redirect” / exceptions profiles (different rule sets) quick modes (temporary behavior changes) transparent logs so you can see what happened I’d love to understand your workflow: Do you want strict per-site control, or “profiles” for contexts (work/travel/social)? Would you use a one-tap “disable for...
Drop your worst “opens the web version instead of the app” link 🙃
I’m collecting real examples where Safari opens the wrong destination: web app instead of native app, AMP pages, social redirect wrappers, short links, etc. If you have a link that consistently behaves badly, please post: the URL (or domain + path pattern) what you expected to happen (which app / which screen) what actually happens in Safari I’ll reply with how I’d handle it (new rule,...
Which apps/domains should I support next?
I’m the maker of Open Links in Apps — an on-device Safari extension (iOS & macOS) that opens supported links in native apps and cleans messy URLs. I’m prioritizing the next batch of “open in app” handlers + redirect rules. Questions Which app links do you most want to open natively from Safari? (e.g., YouTube, Maps, Telegram, Reddit, X, Instagram, Slack…) Which domains are the worst offenders...
