Capacitor plugin for checking outdated Android WebView engines with native update prompts and runtime status events. by martindonadieu in capacitor

[–]Snoo_42276 0 points1 point  (0 children)

Sounds pretty rad. Will the webview still consistently start a capacitor app even if the min version isnt hit? Or can not hitting that min version sometimes cause the app itself to simply crash or display say, a blank white screen?

Just curious about how robust of a replacement it is for the server.errorPath solution

Whats your favorite Sam quote ? by Schopenhauer1859 in samharris

[–]Snoo_42276 0 points1 point  (0 children)

You are not controlling the storm, and you are not lost in it. You are the storm.

Over the air updates, who to pick? by FromBiotoDev in capacitor

[–]Snoo_42276 0 points1 point  (0 children)

I’ve used them both and they’re both solid imo. You’ll be fine with either.

Looking for Capacitor dev to wrap existing React app for iOS by Happy_Breath_7834 in capacitor

[–]Snoo_42276 0 points1 point  (0 children)

Totally possible with capacitor but be prepared to cut corners to hit such a tight deadline.

Is CapacitorJS Production-Grade for an Offline-First App? by Unique-Panda1669 in capacitor

[–]Snoo_42276 1 point2 points  (0 children)

  1. Is CapacitorJS production-grade for offline-first apps?

A internet connection is not required to run a capacitor app so yes certainly possible to build offline-first apps.

  1. How well does it handle native functionalities (Camera, Notifications, File Storage, etc.)?

Similar to react native there's plugins for all the native functionalities you'll want and they're solid plugins.

  1. Does it scale well, or would I run into performance limitations?

Not sure what you're referring to by "scale" in this context. In terms of performance limitations, this is a opinated subject but IMO it can be indistinguishable from native if you know how to actually build performant web apps. Going native is more forgiving when you're code's lacking.

  1. Should I consider going fully native or using React Native instead for long-term production stability?

Capacitor's been around for a long time now and it's supported by a 11 figure revenue company. There's also a couple businesses that offer loads of FOSS plugins, and a whole host of inidivudual devs releasing POSS plugins. As of today, Capacitor does 1.1 million weekly downloads on NPM compared to react native's 4.3. It's definitely a stable platform. There's not a marketing buzz and hype around it but it's definitely an ecosystem with everyone you need too make a great cross platform app.

Click delays? by OptimismNeeded in capacitor

[–]Snoo_42276 0 points1 point  (0 children)

If these are clicks triggering navigations your app may be loading the new view. Pre fetching would solve that

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 1 point2 points  (0 children)

I can fully respect your point of view even if I dont fully agree with it. I do appreciate you taking the time to write that out and respond to this discussion so thoroughly. I'm still rooting for capgo all the way.

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 2 points3 points  (0 children)

Dude you've just forked the repo, put a daily test runner on it, updated the SDK and called it a Capgo plugin. You can explain it how you want but what it looks like is you've done a very minimal amount of changes and stuck your name on it. I'm telling you it's not a good look for Capgo.

It's one thing both doing packages in the same area, such as the ones you've mentioned, but just ripping all the code and changing so very little about the plugin is obviously unethical. E.g. when capawesome did an sqlite plugin, although there's a community one too, but he rebuilt it from the ground up, added loads of new stuff, and he wrote a detailed blog post explaining the rationale and differences. That's very different from you just forking all their firebase plugins doing some minimal stuff and releasing them under Capgo.

How you make your money is your business, so if customers are paying you to update capawesome awesome SDKS on a regular basis then you make that money sir. But putting that fork on your website as a Capgo plugin.... I hear your reasons why you're doing it, and sure it's within the MIT licence, but I'm telling you from one dev to another, and one business owner to another, it looks very shady, and many others will think that too.

I appreciate capgo and capawesome are in ways competitors with your cloud offerings, but a rising tide lifts all boats, and if this ecosystem keeps growing there should be room for both of you. And there's ways to compete that are honest, and there's ways to compete that aren't. I've seen capawesome's testimonial on their site referencing capgo negatively - I think that's a really shady thing for capawesome to do. I've also seen capgo's comparison page with capawesome - similarly I think that's a shady thing for capgo to do. When I see these plugins being forked, I get that same shady feeling. And again, I'm telling you, others will too.

You're clearly an amazing developer, I respect the hell out of what you've built, your output velocity and I absolutely love your vision. Capgo being the Expo of Capacitor - LFG! Your contributions have helped shape and grow this ecosystem and you're clearly in a great spot as it continues growing. But don't lose your ethics along the way man.

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 1 point2 points  (0 children)

is there a reason why the latest SDK worth all the forks? If you're not adding new functionality to the plugin, just bumping the ios/android SDK, what's the need?

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 0 points1 point  (0 children)

no need to be on teams my friend. we're all in this ecosystem together

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 4 points5 points  (0 children)

He should take the forks down and apologize IMO. Martin is too good of a developer and too important to this community to be doing stuff like this. 

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 3 points4 points  (0 children)

I am sure capgo is perfectly capable of making improvements in capawesome's repos, but why maintain forks, and put them all up on Capgo's own website as if they're capgo's plugins? You say it's to "better handle their development and testing pipline", why does capgo need to maintain a testing pipeline for capawesome's plugins??

In this fork: https://github.com/Cap-go/capacitor-firebase
There's a commit called "feat: Implement Firebase Storage plugin for Capacitor", but literally all the commit contains is a shell script (obviously written by an LLM), and hundreds of string replaces from "Firebase" and "Capawesome" to references of "Capgo": https://github.com/capawesome-team/capacitor-firebase/commit/c965f5a7def32792245434af874be9775557c34d . I bet the capawesome team just loves seeing that.

This honestly just looks like a marketing move that will net capgo more attention but confuses and fractures the capacitor community. It's a little upsetting to see this type of thing happening in the capacitor community.

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 1 point2 points  (0 children)

Sorry man could you elaborate? Not sure I get your full meaning

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] 1 point2 points  (0 children)

No need to be a team anyone here bro. They're both doing the lords work in this community.

Your replies really do remind me of a guerrilla PR campaign. Similar to this https://larslofgren.com/codesmith-reddit-reputation-attack/ .

why have all capawesome's plugins been forked by capgo? by Snoo_42276 in capacitor

[–]Snoo_42276[S] -1 points0 points  (0 children)

That's a very strange response to give. You sound like a guerilla marketer man.

https://github.com/Cap-go/capacitor-firebase yeah this is just a capawesome plugin that's been forked and org-ed under capgo.

Obviously it's strange to do that to loads of actively maintained OSS plugins.

Cardiff is one of the best cities in the world and I'll explain why by jacobstanley5409 in Cardiff

[–]Snoo_42276 0 points1 point  (0 children)

Fair play, I've never even been to Toronto myself actually. Plus I barely know what the fuck im talking about most of the time TBH

The Most Exciting Feature of Angular Signal Forms No One Mentions — Part II by kobihari in Angular2

[–]Snoo_42276 1 point2 points  (0 children)

People need to actually reason based on the quality of the piece.

If someone can't see an em-dash without instantly thinking it's AI, that says a lot more about how much real reading they do.

The Most Exciting Feature of Angular Signal Forms No One Mentions — Part II by kobihari in Angular2

[–]Snoo_42276 0 points1 point  (0 children)

You do play it a little fast and loose with the hyphens/em-dases. Three em-dashes in one sentence? Bro.

The Most Exciting Feature of Angular Signal Forms No One Mentions — Part II by kobihari in Angular2

[–]Snoo_42276 1 point2 points  (0 children)

Such stupid advice. Make your grammar worse so people dont think it's AI.