Repository navigation
Replies: 10 comments 12 replies
|
tbh I don't care as long as adm work |
|
btw btw the latest geckview is also match our mid sdk so we got no promlem in min sdk thing |
|
I love this browser because it's pretty, minimalist, lightweight, optimized, and low-battery consuming. It blocks ads and redirects well, besides allowing you to watch videos in an integrated player and download them whenever you want. I had been looking for a browser like this for a long time. In case you decide to make the change, is there no way to keep both versions? 🥹 |
|
I also like clints small footprint.. |
|
Also I don't like Firefox browser on Android.. its super slow. I tried to use it multiple times.. for Example: on the same website, firefox is stuck at leading, I wait and wait.. then I just open chrome and the same website immediately loads on brave or other chrome Browser.. meanwhile Firefox is still loading... it happened so many times that I ditched Firefox on Mobile for good. |
|
What sets Clint apart is its lightness. Embedding Gecko is a radical change that would weigh the browser down, and there are already many browsers built on Gecko—for example, WebLibre, which is a massive customization powerhouse. For me, Clint remains a good open-source option that relies on WebView for browsing without consuming resources, especially after v1.2.0. If it must be done, it can be done by keeping the current Clint and creating a separate Gecko version named, for example, ClintFox, as SmartCookieWeb did. |
|
Also agree.. maybe Clint itself can ve renamed to like Clint webview clintemite.. and keep the webview version maintained for new Android without introducing much of new Features.. |
|
I only want one thing 'the dark view mode' for websites looks like 'webview' not dark reader extension type. thanks.. reply if possible |
|
You can install Dark Reader itself as an extension. Unfortunately, GeckoView doesn't have a force dark mode API, but it does support extensions. |
|
So after thinking about it a lot, I finally made my decision. The Clint we all know and love will stay as it is, but I also want to give Gecko a shot. After I finish migrating Clint to Gecko, I’m planning to make another repo called Clint Browser Gecko or something similar. So basically, Clint Browser will have two versions: Clint Browser — the current one, based on Android System WebView. It will be lighter and will continue to be developed. Clint Browser Gecko — the GeckoView version, where I can go all out and experiment more with what a browser can do. Both versions will still share the same development as much as possible. If I can add a feature to the WebView version, I’ll add it there too. I don’t want the current Clint to just get abandoned because I made a Gecko version. I really hope everyone is okay with this decision. Tbh, I never expected Clint to become this big. I originally made this app for myself. It was literally just supposed to be my personal browser, and I never really planned to build something for a whole community. But somehow the community kept getting bigger, and honestly, that makes me really happy. And now we're getting really close to 100 stars. That's actually crazy to me considering how this project started. So if you like Clint, please consider sharing it with your friends or anyone you think might like it. It would really help the project 💜 |
|
That's Great.. i think you can pick and choose some feature from the gecko version.. don't get overwhelmed while trying to maintain two.. the webview version can remain simple.. |
|
I think this a great route if you have the time to do it. It has to be something specific you wanted to do for a change this bug when youre browser is starting get so popular. What did it stop you from doing if you dont mind me asking? I know what you mean though and its why I run so many different browsers. |
|
So here's a sneak peek. Just finished migrating, but Quiver Guard seems to break the page when I turn it on. I might take a look at it again later that why there an ads, but everything else works fine. I need to go to school now, though. I'm gonna be late
|
|
|
🐐🐐🐐 
|
|
Could you make your native dark theme mode without using extension as I use in webview engine because images in some websites not shows properly, if possible please reply. thanks.. |
|
Unfortunately, GeckoView doesn't provide a native force-dark API like Android WebView does. That's why I can't implement the same dark mode directly, and using an extension like Dark Reader is currently the alternative. |
|
If possible try one of its kind everything possible in these days (I mean you try force dark api or dark mode extension in your language), please i believe you did.. |
|
I understand what you're asking for, but GeckoView doesn't provide a native force-dark API like Android WebView does. Dark Reader already exists as an extension specifically designed for this purpose, so I'd rather recommend using it than reinventing an existing solution. I'm a solo developer maintaining an entire browser, and implementing my own dark mode engine from scratch isn't a practical solution when a dedicated project already does it. |
|
Sorry, no problem, I understand, i'm not forcing you to do, I'm just holding my ground. Thanks for giving me your precious time. |
|
I just don't like giving anyone hope🙂 |
Uh oh!
There was an error while loading. Please reload this page.
I’m considering switching Clint Browser from Android System WebView to GeckoView, Mozilla’s browser engine for Android.
This isn't a small change. Clint is currently built around WebView, so switching the underlying browser engine would require a significant amount of work. I expect the migration to take at least a month, and potentially longer.
Why am I considering it?
As Clint has grown, I've started running into more limitations with Android System WebView.
WebView is convenient because it is already built into Android and provides a Chromium-based browser engine without Clint having to ship its own engine. However, it also means Clint is limited by the APIs and capabilities that Android's WebView provides.
GeckoView is different. It is specifically designed to let developers build their own Android browsers using Mozilla's Gecko engine.
Switching to GeckoView could give me more control over the browser engine and access to browser-specific capabilities that aren't practical or possible with WebView.
One of the biggest things I'm interested in is proper browser extension support. GeckoView could potentially make it possible for Clint to support compatible browser extensions in the future.
It could also make other advanced browser features easier to implement because Clint would have more direct access to the browser engine instead of relying on Android System WebView.
But there are trade-offs
Switching to GeckoView isn't automatically better.
Clint would have to ship GeckoView with the app, which means the download size would increase significantly compared with relying on the WebView already installed on Android.
It could also use more RAM and storage, potentially affect battery life, and have different performance characteristics depending on the device.
There could also be website compatibility differences because Gecko is a different browser engine from Chromium.
Most importantly, I would have to rewrite a significant amount of Clint's existing WebView-related code. During the migration, there could be bugs, regressions, and features that temporarily don't work the way they currently do.
This means choosing GeckoView would be a serious long-term commitment rather than something I could easily undo after a few days.
When would this happen?
I'm not switching immediately.
I want to finish and release Clint 1.2.0 first.
After 1.2.0 is released, I'll use the feedback from this survey, along with the technical feasibility of the migration, to make the final decision.
If I decide to go forward with it, Clint 1.2.1 could become the start of the GeckoView transition.
The transition itself could take a month or more, and development during that period would be heavily focused on migrating, testing, and fixing Clint rather than simply adding new features.
So this isn't a vote on whether I should change one setting.
It's a vote on whether you think the additional capabilities GeckoView could bring to Clint are worth the larger app, potential resource usage, compatibility differences, and significant development time required to make the switch.
13 votes ·
All reactions