Opinion: Web Apps Should Replace Native Apps in Most Use Cases

·1 views

A recently published opinion piece argues that developers and organizations should avoid building native applications whenever a web-based alternative is feasible. The author contends that native apps introduce unnecessary complexity, higher maintenance costs, and platform fragmentation compared to web apps. The article suggests that advances in web technologies have made browser-based applications capable enough to handle most common tasks previously reserved for native software. The piece has gained some traction on Hacker News, though it has not yet generated community discussion.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Handle Notification Taps in Expo Apps Across All Launch States

When a user taps a push notification, the app's entry point varies depending on whether it was terminated, backgrounded, or active at the time. Expo provides two separate mechanisms to cover these cases: getLastNotificationResponseAsync() for cold launches and addNotificationResponseReceivedListener() for background or foreground taps. Developers should avoid triggering navigation before authentication checks or the Navigator is fully ready, as this can cause routing conflicts. To prevent duplicate listeners during screen remounts or Fast Refresh, the listener subscription should be cleaned up with remove(). For security, externally provided URLs should be validated against allowed hosts and converted to internal routes before being passed to the router.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google, Bing, and Brave Agree on Top Search Result Only 29% of the Time

A comparative analysis of 15 searches run across Google, Bing, and Brave found that all three engines agreed on the number-one organic result only 29% of the time. On average, Google and Bing shared just three of their top-ten results, while Google and Brave overlapped on about five. Each engine showed a distinct content preference: Google heavily featured its own properties like YouTube and Reddit, Bing favored traditional publishers such as Forbes and PCMag, and Brave fell somewhere in between. Notably, Reddit, YouTube, and Wikipedia appeared in none of Bing's top-ten results, despite featuring prominently on Google. The findings highlight that tracking search rankings on a single engine gives an incomplete picture of overall search visibility.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Flutter Code Generator Hit by Riverpod's Dual build() Signatures in ConsumerState

A developer building an automated Flutter app generation pipeline discovered a costly bug involving Riverpod's ConsumerState class, which incorrectly received the two-argument build(BuildContext context, WidgetRef ref) signature valid only for ConsumerWidget. Dart's error message framed the issue as a generic inheritance complaint, obscuring the Riverpod-specific root cause and causing the automated repair loop to exhaust all three retries without resolving it. The pipeline, sourced under an MIT license on GitHub, generates Flutter apps from a spec file and uses flutter analyze output to drive an automated fix cycle. The developer resolved the issue by routing diagnostics to the appropriate agent based on whether the error was UI-anchored or state-anchored, rather than blindly retrying the same agent. As a demonstration of the system's output, the repository includes 23 unmodified generated files produced from a 45-line spec.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Playwright's check() can silently fail on JavaScript-driven select-all checkboxes

A subtle automation bug in WordPress plugin and theme update screens causes Playwright's check() method to appear successful while individual checkboxes remain unchecked. This happens because check(force=True) updates only the target checkbox's DOM state without guaranteeing the JavaScript handler responsible for propagating the selection actually fires. As a result, clicking the update button submits an empty selection with no error thrown, making the test run look normal when nothing was updated. The recommended fix is to verify the checked state of individual checkboxes immediately after calling check(), and fall back to selecting each one manually if the select-all had no effect. Because WordPress plugin and theme update screens share the same structure, this verify-and-fallback pattern must be applied consistently across all affected screens.

0 comments Read more at DEV Community