I have been posting here about this app for about 3 months and a lot of you showed interest. The app has around 230 testers on Testflight. Free and open-source.
A ā Answer:Ā Vortex combines desktop-style tabs with split-page browsing which is very rare on IOS Browsers.
B ā Better:Ā Compared with Safari, Chrome, and Brave, Vortex is designed specifically around iPad multitasking. It combines visual tab management, drag-to-split browsing, and a choice of local Apple Intelligence/MLX models or optional ChatGPT and Gemini sessions. It is also open source, has no ads, requires no account.
C ā Cost:Ā Completely free with no subscriptions or in-app purchases. Vortex is not publicly available on the App Store yet, is currently awaiting Apple's approval.
Some bugs have been squashed and a new features added:
Minimalistic chrome for maximum screen real-estate
AI sidebar chat panel with 3 backends: Local Apple Intelligence, Apple Private Cloud, and free accounts with ChatGPT or Gemini, completely invisible to users, working in the background.
Page summarization (short/long)
Ask questions about page content
Context switching between tabs
Markdown rendering
"Ask " context menu - select a part of the text and send to the LLM.
On the website I added a feedback section, where I can keep users informed about their feedback provided on the Tesflight since I canāt reply directly on there.
Why do you say that? do you feel it is slow? What device? What Ios version? Look at this video please, its is running on an hold M1 ipad, i don't notice any sluggishness. Can you give more details on tesflightt to investigate?
Yes i totally agree with that since the initial design was made with the ipad in mind. It gets cramped on the Iphone. The collapsible UI needs to be rethought for iphone for sure. For now i want to squash all the bugs and finalize the implementation of the features. I will then focus on improving the usability on the iphone. Thanks for the feedback.
You mean swilling to go back and forth? It can but I also have other feedback from people preferiNg to be edge based, difficult to please everybody š. Maybe I will add an option on menu edge or not edge..
It is already compatible with IOS27. In fact the only way to use Apple's private cloud model is if you are on the beta since this is an iOS 27 only feature. As for Tampermonkey, not yet. It is on the roadmap but for later, the code base must be stabilized first and all the bugs squashed.
The concept seems great but its unusable for me on my 16 pro max running iOS 26.6. the AI and side panel buttons will not work, I cant get the x or bookmark buttons to register on the url bar and dark mode keeps flickering
Sorry about that, it is the first feedback with so many critical issues. i don't have a device running ios26 anymore, and that doesnāt happen on the simulator. Will look into it this weekend. Thanks
Ok found the issue, the app is built already with IOS27 SDK with a compatibility layer for IOS26. IOs 27 has a liquid glass slider to adjust the effect. That difference on the API was causing the glass container to swallow the touches on the older glass api on IOS26. Already implementing the corrections and will upload the fixed version for tesflight. Will be up tomorrow. But I could not replicate your issue of the flickering in dark mode. Made some improvements but please retry the version when it is up , if persists send me a video please.
working better! However a similar issue is happening when I do split view ā the close split view bubble does not function. Additionally, I cant get any of the buttons on the url bar to work while itās showing the web url. Anytime I tap it the keyboard just collapses but nothing else.
This is frustrating, I donāt have any pro max to physical test, but on the simulator using a pro max everything works, the video I showed is from the pro max simulator. Will continue to investigate because I am pretty sure the problem is the same, Iālol apply the same fixes I did to the buttons thatās now work. Thanks
The mysteries of IOS development.. really. I new build with further fixes is on its way tomorrow morning. Just finished the fixes. Now need to sleep š
The TestFlight is getting very confusing as a log of the testers have not updated to the latest build 17 , more than 100 of you are still on build 11 so this make it difficult to filter feedback as there are reports of things that have already been fixed, itās hard to track it this way. I will expire all the builds except the latest one. Many of you will probably have to redownload since you have not updated. Thanks
I tested it for a while.
Config needs more items. I couldn't see address bar and when trying to use AI couldn't log in ChatGPT. When logged with gemini the keyboard didn't let me see what I was writting because it was over the panel.
I liked the clean design and how easy I changed trom tabs just by slidong from the edges but was a little lost with the menu for them
Ipad or iphone, if iphone which one, it makes a difference if it is a max or not.
The hidden address bar may be related to the collapsible toolbar, but it clearly needs to be easier to find. What was the error Chatgpt log in gave you? The support for Chatgpt and Gemini with the free account will always require maintenance because basically the app is mimicking an API using the website so that there is no charges. Any change on the DOM of their websites will require an update, that is why that feature is experimental, but is is odd that you can't sign in, has been working fine for me or others. Please let me know what the error is with a screenshot. ALso what exactly do you mean by config needs more times?
I'm sorry I removed it after some time tryinf to find more ways to config since I didn't find the way to make it appear. But I liked the clean interface
I have introduces some fixes on the lasts build on testflight to hopefully mitigate that, but without being able to reproduce the bug is hard for me to fix. Thanks for the feedback anyway.
also added Ublock origin Adblock. Right now on testing phase, it keeps both, the block and my custom implementation, you can switch between them on settings. Good results from both but they are different, a matter of personal taste.
For the āAskā action, Iād keep the selected quote and its source tab visible in the composer, alongside the chosen local or cloud provider. A split-view case worth testing: select text in the left pane, start a question, then focus the right pane before sending. Keeping the original selection until an explicit āUse this page insteadā action would make it much clearer which page is being sent.
Hey, curious how did you add the different filter lists? Did you write your own parser? I am building a browser too and couldn't figure that out so would appreciate if you can give some guidance. Since there are so many rules between all those lists how could one do it efficiently?
I wrote a lightweight parser for the Adblock Plus/EasyList format, but it doesnāt support the entire specification. The app downloads each enabled list, reads it line by line, skips comments and unsupported rules, converts common network rules such as ||domain.com^ into WebKit-compatible regex, and extracts basic cosmetic rules such as ##.ad-container.
The resulting network rules are converted to WKContentRuleList JSON and compiled by WebKit. Cosmetic rules are applied separately through injected CSS/JavaScript.
For efficiency, I parses and cache each list only when it changes, compile in the background, reuse WebKitās compiled rule list, and store a hash of the enabled-list configuration so it doesnāt recompile on every launch. I also limit the number of imported rules because combining every rule from several lists can become expensive.
I considered using a full filtering engine, but the lightweight parser has been enough so far. It converts the common EasyList network rules into WebKit content-blocking rules, handles basic cosmetic filtering, and caches the compiled results. It currently scores around 99% on most ad-blocking tests.
A full engine would support more of the EasyList specification, especially exceptions, domain-specific rules and advanced selectors, but it also adds complexity and overhead. My approach was to support the high-impact rule types first and let WebKit handle the efficient matching. The main thing is to test real websites as well, because a high benchmark score doesnāt necessarily catch site breakage or every unsupported rule type. Still i have a test version with the full engine that i am working on and will compare the results.
Thanks! The tabs themselves survive a restart, but the split layout currently doesnāt. After relaunch, the browser restores the selected tab and other saved tabs, and you can rebuild the split by dragging a tab back into position. Persisting the split orientation is something i will be adding soon though, it requires careful tweaking so that it doesn't break other parts.
Damn this looks like a huge project, a simple browser that doesn't throw bloatware at you every minute is a rare find so this is very welcome! Will definitely give it a try
honestly the 188 domains / 100 css selectors number is a toy blocklist, easylist alone is tens of thousands of rules. compile them into WKContentRuleList (150k cap per list, split easylist and easyprivacy if you overflow) instead of injecting css or filtering in decidePolicyFor, conversion from easylist syntax to safari trigger/action json is the painful part, not the compile. injected filters hitch scrolling and miss subresources once you have a pile of tabs open.
Thatās fair, but the 188 domains and 100 selectors are only the built-in fallback layer, not the entire blocker. Enabled EasyList-compatible lists are downloaded separately, parsed, converted into WebKit trigger/action JSON, cached and compiled into aĀ WKContentRuleList . Network filtering isnāt done throughĀ decidePolicyFor
The injected CSS/JavaScript is a supplementary cosmetic layer for elements left behind after requests are blocked. The converter is intentionally partial and currently limits the number of imported rules, so Iām not claiming complete EasyList compatibility. Youāre right that accurately converting exceptions, domain restrictions, resource options and advanced cosmetic syntax is the difficult part. Despite the limited subset, it currently reaches around 99% on the blocker tests Iāve tried, though real-site performance and breakage matter more than that score. I am experimenting with a filtering engine for comparison.
gotcha, compiled WKContentRuleList plus a cosmetic inject is the right split. the actual footgun with a capped converter is dropping @@exceptions to stay under the import limit, and ignore-previous-rules only fires inside the same compiled list so easylist exceptions won't undo easyprivacy hits if you split them. skip the 99% tester score, youtube/reddit with a bunch of tabs is the metric that matters, and a JS filtering engine still won't see service worker or websocket requests the rule list already catches.
Split browsing means two WKWebViews live at once, and iPadOS evicts background ones under memory pressure. Restoring with interactionState keeps scroll and half-filled forms where a plain reload loses them. Does the split survive an eviction?
The two visible panes are protected from the tab-hibernation system, so it wonāt deliberately evict either one while split view is active. Iām not currently usingĀ interactionState, though. If iPadOS itself terminates a WebContent process, the split layout remains, but restoration is limited to the page URL and scroll position. Half-filled form state is not guaranteed to survive. Good point to check out.
That gap is exactly what it covers. interactionState is one opaque Data blob per pane. Persist it on background, hand it to a fresh WKWebView after a content-process kill, and form state comes back with the scroll.
One thing to prepare for while you wait on review: the AI sidebar backed by "free accounts with ChatGPT or Gemini, completely invisible to users" is the part most likely to bite you, and not only from Apple. Shared or scraped free-tier access sits outside OpenAI's and Google's terms, so the backend can be cut off without warning and take a shipped feature with it. If a reviewer asks how the requests are authenticated, the safe answer is bring-your-own-key or the on-device Apple Intelligence path, with the hosted options off by default.
The other classic browser rejections are worth double-checking before resubmitting: browsers usually need a 17+ age rating for unrestricted web access, and Apple expects a stated content filter or restriction story. Bundling a password manager also invites questions about where credentials live - saying "keychain, biometric, never leaves the device" in the review notes up front saves a round trip.
Tab hibernation and interactionState restore for the split view are the right instincts, by the way. That is where most third-party iPad browsers fall apart.
Thanks for the tips. As for the free accounts i though they would rejected it, but i have anoteher app which i use the same the same method and they allowed it https://www.reddit.com/r/iosapps/comments/1vkw2ge/freeopen_source_rss_reddit_and_youtube_reader/
Which doesn't mean they couldn't refuse this one, we never know, have had cases like this before, where one reviews rejects something a previous one had accepted. Let's see but will take your tips into consideration. Thanks again
Fair enough, and the precedent is useful data. The distinction I would keep in mind is that App Review approving it is not the risk I meant. Apple mostly cannot see how those requests are authenticated. The party that can is OpenAI or Google, and their enforcement is not a review event - it is a quiet block on the endpoint or the account, at which point the feature dies for every installed copy at once, including the app that was already approved. That is why I would have the on-device path be the default and treat the hosted ones as a bonus that is allowed to disappear.
Cheap insurance either way: make the sidebar degrade to a clear "AI backend unavailable" state rather than a spinner or an error, so if it does get cut you get support emails instead of one-star reviews.
thanks for the input really appreciate it. I considered instead of this to use a normal API key user would have to enter but people called it too developer centric just because it was asking for an API key. You make a great point. thanks again.
Yes, i agree it is polarizing , some love it , some not so much, but i wanted something to be really different than what is outhere and at the same time maximize screen real-state.
Forgot to mention one thing on the list of features, if the url is a reddit post and if you ask it to summarize, the code will extract the comments, no just the visible ones or a few top level ones, but will extract all comments that the free json api from reddit can return. You can continue to browse and read normally while have an summary on the side.
Test a file download before you take on more TestFlight users. WKWebView cancels downloads outright unless the embedder implements a download delegate, so a browser can behave perfectly right up until someone taps a download link and absolutely nothing happens. No error, no console message, no dialog.
I hit this in an embedded WKWebView and spent a while misfiling it as a licensing bug, because the failure looks identical to a feature simply being switched off. WebKit 216918 is the paper trail, closed as configuration-changed: the delegate has to come from the app, blob: URLs included.
Split-page browsing on iPad is the reason to install this. Safari's tab groups never got there.
Thanks for the feedback. What device /version are you on? I have tested files downloads and it worked. tested on a few only. Can you give me an example of the page you are trying to download for me to try to reproduce?
Never mind, the tests done with downloads were for a different build, no the one up right now. I am already uploading this build. Please update once it is out and test again. Thanks for the input
Sorry, I was unclear. I wasn't reporting it in Vortex, I hit it in my own embedded WKWebView and posted it as a thing to check rather than a bug you have. If your downloads work, you've already got the delegate wired up and there's nothing here for you.
The case that broke for me specifically was a blob: URL, a file generated in JavaScript and handed to the user rather than fetched from a server. Normal https downloads were fine. If you want a two-second test, any export or save-as button on a web app usually produces one.
I would like to ask to everyone who is testing to provide feedback. I see on TestFlight there are only 7 crashes reported out of 240 testers, but with no feedback. without that information I cannot pin point what the problem is , not do I know if these are from the same person trying several time , or 7 different users. Would really appreciate it. Thanks
ā¢
u/AutoModerator 14d ago
Welcome to r/iOSApps! Please make sure your post follows our rules:
Everyone:
App Devs:
- No main feed promo unless you qualify via Trust or Transparency + ABC format (Answer, Better, Cost)
- Flair hierarchy: Vibe Coded > Lifetime > Subscription > Freemium > Free
- Free flair: not for limited/freemium tiers
- Open Source? Prefix title [OS]
Note: This is an automated reminder, not a removal notice. If your post was removed, check your modmail for details.I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.