# mobile web Published articles for mobile web. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## TikTok Is Quietly Putting Web Apps Inside Its App DevFeed: [TikTok Is Quietly Putting Web Apps Inside Its App]() Original publisher: [Read original article]() Author: Alex Harper Published: 2026-09-10T17:33:18Z Content type: article Language: en Sources: [Web Designer Depot]() Topics: [modern web development](), [Web Development](), [interactive website](), [App](), [React Native]() Tags: [app-development](), [app-ecosystem](), [browser](), [digital-platforms](), [embedded-apps](), [framework](), [future-of-apps](), [in-app-experiences](), [javascript](), [mini-apps](), [mobile-apps](), [mobile-web](), [platform](), [react](), [social-commerce](), [social-media](), [technology](), [tiktok](), [tiktok-apps](), [tiktok-developers](), [ui-design](), [ux-design](), [web](), [web-apps](), [web-design](), [web-designers](), [web-development]() ### AI overview TikTok Minis let third-party, web-based experiences run inside TikTok, using technologies such as HTML, JavaScript, React, and Vue. The article examines how this could blur the boundaries between websites, social networks, and apps while noting TikTok's platform, configuration, and approval constraints. ### Source excerpt TikTok isn't just hosting videos anymore--it's quietly letting web-based experiences live inside the app. TikTok Minis could blur the line between social network, browser, and app platform, and web designers should be paying attention. ## \*FLAILS AROUND\* SUMMER SPECIAL! JOIN NITRO, GET AN EXTRA MONTH OF NITRO ON US! DevFeed: [\*FLAILS AROUND\* SUMMER SPECIAL! JOIN NITRO, GET AN EXTRA MONTH OF NITRO ON US!]() Original publisher: [Read original article]() Author: Wumpus Published: 2025-07-08T00:00:00Z Content type: article Language: en Sources: [Discord Blog]() Topics: [Discord](), [Android](), [Web app]() Tags: [2025](), [android](), [desktop](), [discord](), [mobile-web](), [promotion](), [upgrade](), [web-app]() ### AI overview Discord announces a summer promotion running through July 15, 2025. Eligible users who start a new monthly Nitro membership receive a second month of Discord Nitro at no additional charge. ### Source excerpt NITRO, NITRO, NITRO! From now until July 15th, 2025, if qualifying users start a new monthly Nitro membership, they'll get a SECOND month of Discord Nitro to top 'em off! ## Managing Recurring Payments with Apple Pay Using PayPal DevFeed: [Managing Recurring Payments with Apple Pay Using PayPal]() Original publisher: [Read original article]() Author: PayPal Tech Blog Team Published: 2023-11-20T14:41:42Z Content type: article Language: en Sources: [PayPal Technology]() Topics: [SDKs](), [Mobile](), [Transactions](), [Authorization]() Tags: [apple](), [apple-pay](), [authorization](), [js-sdk](), [mobile-web](), [payments](), [subscriptions](), [token](), [transactions]() ### AI overview This article explains how merchants can support recurring payments with Apple Pay through PayPal's JS SDK and V3 Vault experience on mobile websites. It covers fixed or variable billing, consent details, authentication, transaction outcomes, and persistent tokens for future purchases. ### Source excerpt Recurring payments have become an integral part of the modern digital economy, offering convenience and predictability for both consumers and businesses. Our previous post highlighted different methods of integrating Apple Pay® with PayPal. This blog explores recurring payments using PayPal and Apple Pay, showing how using it can streamline transactions and benefits end users. How Recurring Payments with PayPal and Apple Pay Work A recurring payment is an agreement between a buyer and a merchant. It allows the merchant to charge the buyer's chosen payment instrument (typically a credit card) for a pre-approved amount at pre-approved intervals, which can be either fixed or variable. Consumers visiting a merchant's mobile website integrated with PayPal JS SDK and V3 Vault experience will find Apple Pay as one of the available payment methods for recurring payments. Once the consumer taps the Apple Pay button on the mobile website, the Apple Pay payment sheet is presented. This process mirrors the one-time Apple Pay experience for mobile web transactions. The merchant's website plays a crucial role in detailing the billing frequency and other terms of service. These details can also be reiterated on the payment sheet for added clarity. Recurring fees can take two forms: fixed amounts, such as monthly movie ticket subscriptions, or variable amounts like weekly grocery orders. The variability is subject to local authorizations. Depending on the specific merchant use case, customers may be presented with line items that reiterate billing frequency, discounts, and any additional upfront fees on the consent screen. To ensure transparency, the final payment amount is prominently outlined on the total line, making customers fully aware of the charge they are authorizing. The consumer can review the transaction details on the Apple Pay payment sheet. Once the consumer is ready, they authenticate using Face ID® or Touch ID®. When the transaction is complete, the consumer is sho ## A blog redesign and an exploratory Rust multiplayer game project DevFeed: [A blog redesign and an exploratory Rust multiplayer game project]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2021-07-29T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [border-image](), [Media Queries](), [Rust](), [WebAssembly](), [Web Development](), [WebRTC](), [Bevy](), [render]() Tags: [bevy](), [css](), [life](), [mobile](), [mobile-web](), [render](), [rust](), [wasm](), [webassembly](), [webrtc]() ### AI overview The author describes updating the blog with responsive CSS and migrating comments to GitHub issue comments while experimenting with a browser-based multiplayer game in Rust, WebAssembly, WebRTC, and Bevy. ### Source excerpt I have dragged my blog, kicking and screaming, into the era of media-queries and responsive CSS. So now it's readable on a variety of screen sizes. My first post was roughly the same year the iPhone 3G came out I think, and the mobile web wasn't really a big deal back then. ## Next.js 8.1 DevFeed: [Next.js 8.1]() Original publisher: [Read original article]() Author: Tim Neutkens Published: 2019-04-16T21:41:57Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [React](), [Web Development](), [Mobile](), [Caching]() Tags: [cache](), [google](), [mobile-web](), [next-js](), [react](), [render](), [routing](), [speed](), [web]() ### AI overview Next.js 8.1 adds per-page AMP support, enabling developers to create AMP pages with React components and adopt AMP incrementally. It provides hybrid pages that retain the existing version while serving AMP to search engines, as well as AMP-first pages for the main site. ### Source excerpt Next.js 8.1 introduces AMP support on a per-page basis, allowing incremental adoption of AMP. ## Mobile Web Performance @ Caviar DevFeed: [Mobile Web Performance @ Caviar]() Original publisher: [Read original article]() Author: Evelyn Chan Published: 2019-03-28T22:46:49Z Content type: tutorial Language: en Sources: [Square Corner Blog - Medium]() Topics: [Mobile](), [Web](), [Webpack](), [Latency](), [React](), [Rails]() Tags: [caviar](), [engineering](), [javascript](), [mobile](), [mobile-web](), [performance](), [programming](), [rails](), [react](), [web-development](), [web-performance](), [webpack]() ### AI overview This article describes Caviar's effort to improve mobile web performance after recognizing that its website had been built primarily for desktop. It focuses on auditing the home page with Google Lighthouse and examining the React/Rails front-end bundle with Webpack and Webpack Bundle Analyzer. ### Source excerpt Heads up, we've moved! If you'd like to continue keeping up with the latest technical content from Square please visit us at our new home https://developer.squareup.com/blog Across any e-commerce website, page load times are directly correlated with conversion rate. Faced with a page that takes longer than 3 seconds to load, 53% of users drop off, perhaps never to return. A 1 second delay in load time results in a 7% loss in conversions, 11% fewer page views, and 16% decrease in customer satisfaction. In terms of SEO, slow page speeds also impact indexing algorithms, which hurt crawl efficiency and leads to fewer pages being indexed. For consumers on mobile, slow speeds are even more painful. As more and more consumers move towards a mobile first experience, we need to optimize for speeds that don't necessitate blazingly fast internet or even 4G speeds. Typically, improvements in this area means managing your requests and what you load better and more efficiently. This mobile first perspective is top of mind for Caviar as we expand to new markets this year. During our adoption of this methodology, we started noticing that trying out new features on mobile web seemed to take unusually long. We realized that our mobile web experience was far from ideal as the Caviar website was originally built for desktop. The shift in perspective from desktop to mobile was not a clean switch from a developer standpoint as we naturally have more resources for web and are less likely to test for mobile. We mapped out the core webpages on our user's critical path and decided to focus on the starting point: our home page. This is the page most visitors of trycaviar.com start off on and remains one of our most trafficked pages. We used Google Lighthouse to audit our home page as a baseline and full disclosure -- it was not pretty. Our initial Lighthouse audit.Setting Up Metrics At Caviar, our stack includes React/Rails on our web interface bundled with Webpack, a build tool commonly used ## Shopify Merchants Will Soon Get AMP'd DevFeed: [Shopify Merchants Will Soon Get AMP'd]() Original publisher: [Read original article]() Author: Haani Bokhari Published: 2016-09-20T19:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Google](), [Web](), [Open Source](), [App]() Tags: [app](), [checkout](), [google](), [mobile-web](), [open-source](), [shopify](), [web]() ### AI overview Shopify describes its involvement with the AMP Project, an open source, Google-led initiative designed to improve mobile web performance by reducing slow-loading content. Shopify has developed an alpha app that lets selected merchants serve AMP versions of their products, helping mobile customers move from Google search results to checkout in two taps. ### Source excerpt 1 minute read Today we're excited to share our involvement with the AMP Project. Life happens on mobile. (In fact, there are over seven billion small screens now!) We're not only comfortable with shopping online, but increasingly we're buying things using our mobile devices. Delays can mean the difference between a sale or no sale, so it's important to make things run as quickly as possible. AMP, or Accelerated Mobile Pages, is an open source, Google-led initiative aimed at improving the mobile web experience and solving the issue of slow loading content. (You can learn more about the tech here.) Starting today, Google is pointing to AMP'd content beyond their top stories carousel to include general web search results. ## Browser statistics June 2015 DevFeed: [Browser statistics June 2015]() Original publisher: [Read original article]() Author: Henning Spjelkavik Published: 2015-06-25T23:00:32Z Content type: article Language: en Sources: [Finn.no]() Topics: [browser](), [browsers](), [Mobile](), [Google Search](), [Web](), [Internet Explorer]() Tags: [android](), [apple](), [browser](), [desktop](), [devices](), [google](), [google-search](), [internet-explorer](), [iphone](), [mobile](), [mobile-web](), [statistics](), [web]() ### AI overview FINN.no's June 2015 statistics show that smartphones and tablets accounted for 62% of visits, while desktop and laptop visits accounted for 38%. Responsive mobile web was the largest FINN.no application category, and Apple led the browser-vendor ranking. ### Source excerpt In July 2013 more than 40% of the visits to FINN.no were from a tablet or a phone. Nearly one year later, in April 2014 - the share was 48%. What do you think has happened the last year? In April, Google rolled out their "mobile-friendly update", which boosts the ranking of sites that are mobile friendly in the Google search. We're clearly not the only one seeing the increased market share of mobile devices. How many visitors use a desktop or laptop? Our first graph shows the share of our users using a mobile phone, tablet or a desktop computer to access FINN.no, regardless of whether they use the traditional somewhat-responsive-desktop-web (www.finn.no), our responsive mobile web (m.finn.no) or an Android or iPhone app. 62% of our visits are now from a smartphone or a tablet. The traditional desktop/laptop has a market share of 38%. Which FINN.no application do people use? We have three major versions of FINN.no - the desktop, the responsive m.finn.no, and native apps. Our reponsive site is now the biggest! 14% of our visits are from our native apps, 42% from www.finn.no, and 44% from our responsive m.finn.no. Browsers First of all, let's take a look at the numbers of the browser vendors. The ranking is clear, Apple is the biggest, ahead of Google, Microsoft and Mozilla - and Opera is still in the top 5, representing more than an amazing 0.2% of our visits. Do you remember the "browser wars"? When IE 8.0 ruled the web? In case you wondered which browser is the biggest on the "desktop" here's the trend: The complete browser statistics, across all applications are as follows: It seems like a good idea to make sure your website works well with Safari! In case you still have Internet Explorer 9 as your favourite, it's still making it to the top 15, with a total share of 1.2% of our traffic, marginally behind Internet Explorer 10 with 1.4%. In 2015, poor IE8 is down to 0.3%. Thanks to Tobias Flatin, Chris Searle, Gregers G Rygg, Trond Hjorteland, and others for feedback ## Writing your own Karma adapter DevFeed: [Writing your own Karma adapter]() Original publisher: [Read original article]() Published: 2013-09-09T00:00:00Z Content type: tutorial Language: en Sources: [SoundCloud Backstage Blog]() Topics: [JavaScript](), [Web app](), [Continuous integration](), [browsers](), [Web Development](), [Chrome]() Tags: [browsers](), [chrome](), [ci](), [html](), [javascript](), [mobile-web](), [testing](), [web-app]() ### AI overview This tutorial explains how to write a custom Karma adapter for the Tyrtle JavaScript unit testing framework. It covers connecting test results and completion status to the Karma API, creating a renderer or reporter, configuring the test files and runner, and handling Karma's browser-serving and caching behavior, including use with an AMD loader. ### Source excerpt Background When we started to work on the new version of our mobile web app, we knew we wanted to run unit tests on a wide variety of... ## Graded browser support version 1.1 DevFeed: [Graded browser support version 1.1]() Original publisher: [Read original article]() Author: espen Published: 2011-06-27T13:41:23Z Content type: article Language: en Sources: [Finn.no]() Topics: [browser](), [browsers](), [Mobile](), [Website]() Tags: [browser](), [browsers](), [ipad](), [mobile](), [mobile-web](), [phones](), [updated](), [version]() ### AI overview The article announces version 1.1 of the company's graded browser support matrix. It simplifies browser version targeting, adds support guidance for the mobile web service m.finn.no, and includes tablets in the desktop service matrix. Android-powered devices are not supported. ### Source excerpt We have reworked our graded browser support matrix which was released last year. Following the Laws of Simplicity we reduced the complexity in order to make it easier for everyone at our company to understand. We cut a lot of the version number into targeting latest for browsers which are frequently updated. There is also a support matrix for mobile phones which is targeting our new mobile web service m.finn.no. In addition to updating the versions we have also made the decision to include tablets in the support matrix for our desktop verison of our service. This is because we are currently not looking at creating specialized versions for tablets and our service works just fine on the tablets currently hitting our site. Currently almost all of our trafic is coming from iPad's, therefor Andoid powered devices are not supported. ## FINN.no developers present mobile development approaches and the m.finn.no mobile web beta DevFeed: [FINN.no developers present mobile development approaches and the m.finn.no mobile web beta]() Original publisher: [Read original article]() Author: espen Published: 2011-02-01T19:08:24Z Content type: opinion Language: en Sources: [Finn.no]() Topics: [Mobile](), [Web Development](), [iOS]() Tags: [compatibility](), [front-end](), [ios-development](), [mobile](), [mobile-development](), [mobile-web]() ### AI overview FINN.no developers presented different approaches to mobile development, including the beta of the m.finn.no mobile web service. The article discusses development challenges across mobile devices and design decisions for presenting information. ### Source excerpt The title of this post is of course a blatant lie. Mobile development is nothing but pain from here until eternity (no, not really). But, luckily the brave developers at FINN.no aren't scared of a little pain and therefor we decided to do a mobile development trippel header gig to showcase some of the different approaches to mobile developement.Due to some kids falling ille we had to reduce the show to be a double header. It did not end up to make a difference as the guys doing the talks totally kicked ass! Oh and the picture on the left is a flyer we put up everywhere to market the event at the FINN.no headquarters. Finnfrontend is a name for one of our communities of practice dedicated to front-end development. Unfortunately it was reduced to a double header and we missed out on getting the low down on iOS development of native apps. Mobile web on m.finn.no Frank and Sven Inge from Team Mobile at FINN.no presented the beta for m.finn.no. As announced previously on labs.finn.no[Gone] the beta for our mobile web service is now available for testing and feedback. We are very excited about this application and we feel that it takes mobile web to a new level here in Norway. Frank presented some of the plans going forward with the beta (which I am not going to tell here). He also shared some of the experiences and pains with developing for mobile devices. Naturally there are quite a few challenges with compatibility and providing a consistent look and feel across multiple platforms. This has been the bread and butter for web developers for years and it is no surprise that it is hard on mobile devices. The Team also talked about some of the design decisions they have made and why they ended up solving a challenge a certain way. Choosing to display all information and letting the user scroll as opposed to applying the show/hide-style functionality we are used to from the desktop web seems like a really good choice. The mobile web solution looks awesome and we can not wait