Development of SEO optimized PWAs<\/h1>\n<\/div>Portal applications are implemented by us as high-performance, SEO optimized Progressive Web Applications (PWA) with ServiceWorker integration and Server Side Rendering (SSR) from a Universal Server. PWA is the state-of-the-art standard for modern, device-independent web applications that can be permanently installed on the client and have the same user experience as device-specific native applications.<\/p>\n<\/div>
![\"Development](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2020\/04\/Entwicklung-von-SEO-optimierten-PWAs.jpg\" "\\"Development")
<\/span><\/div><\/i><\/span><\/div>100%<\/h2><\/div><\/div>SEO optimized portal landing page<\/div><\/div><\/div><\/i><\/span><\/div>100%<\/h2><\/div><\/div>Native-like User Experience<\/div><\/div><\/div><\/i><\/span><\/div>100% <\/h2><\/div><\/div>Device-independent and high-performance<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>One of the major challenges in developing responsive, dynamic, feature-rich web applications with high user interaction is load-time performance. This means accelerating the “time to paint” and “time to interactive” and thus successfully implementing initial contacts in particular. When a user first views a website, every second determines its success – depending on your target audience, every second 10% of visitors lose interest in your application and bounce. Under real network conditions, how long does it take for the visitor to see the application in the browser – and when can an interaction take place? Repeat visits should ultimately be accelerated even further for an optimal user experience, and basic functions should be maintained even in the event of network failure or in a dead zone, i.e. offline.<\/p>\n<\/div>
- <\/i><\/span>Time to paint (FP, FCP, FMP, LCP)<\/div><\/li>
- <\/i><\/span>Time to interactive<\/div><\/li>
- <\/i><\/span>\n
Responsive<\/p>\n<\/div><\/li>
- <\/i><\/span>Bundle size<\/div><\/li>
- <\/i><\/span>Performance<\/div><\/li>
- <\/i><\/span>SEO, indexability<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
i18n & l10n, a11y<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Offline Mode<\/p>\n<\/div><\/li>
- <\/i><\/span>Event Management<\/div><\/li>
- <\/i><\/span>Events<\/div><\/li>
- <\/i><\/span>Hotel industry<\/div><\/li>
- <\/i><\/span>Hospitality<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>The application was implemented as a Progressive Web Application (PWA) based on the latest frontend technologies: Angular 9 Universal with Server Side Rendering (SSR) and ServiceWorker. This means that the application is rendered in advance by the server as a static HTML page and delivered and displayed to the visitor, while during the following seconds it is rehydrated under the hand – imperceptibly for the visitor – i.e. seamlessly replaced by the dynamic application. The first contact sees – even in poor mobile network conditions – the complete website within about 2 seconds. As soon as the visitor has visually captured the page a few seconds later and starts interacting, the application is launched and ready to go. This conveys an impression of immediacy that welcomes the user and holds his attention. Any further navigation of the visitor with the application is then handled by the ServiceWorker on the client side, or additional components or resources are loaded as needed. An integration of Ionic 5 as well as Capacitor or Cordova was considered, but discarded as not necessary based on the specific project requirements and the existing nativeness given by the PWA properties.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
![\"austin](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2019\/10\/austin-distel-gUIJ0YszPig-unsplash.jpg\")
<\/div><\/div><\/div>![\"nesa](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2019\/10\/nesa-by-makers-vII7qKAk-9A-unsplash.jpg\")
<\/div><\/div><\/div>![\"austin](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2019\/10\/austin-distel-Imc-IoZDMXc-unsplash.jpg\")
<\/div><\/div><\/div><\/div>
Portal applications are implemented by us as high-performance, SEO optimized Progressive Web Applications (PWA) with ServiceWorker integration and Server Side Rendering (SSR) from a Universal Server. PWA is the state-of-the-art standard for modern, device-independent web applications that can be permanently installed on the client and have the same user experience as device-specific native applications.<\/p>\n<\/div>
<\/span><\/div>100%<\/h2><\/div><\/div>SEO optimized portal landing page<\/div><\/div><\/div><\/i><\/span><\/div>100%<\/h2><\/div><\/div>Native-like User Experience<\/div><\/div><\/div><\/i><\/span><\/div>100% <\/h2><\/div><\/div>Device-independent and high-performance<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>One of the major challenges in developing responsive, dynamic, feature-rich web applications with high user interaction is load-time performance. This means accelerating the “time to paint” and “time to interactive” and thus successfully implementing initial contacts in particular. When a user first views a website, every second determines its success – depending on your target audience, every second 10% of visitors lose interest in your application and bounce. Under real network conditions, how long does it take for the visitor to see the application in the browser – and when can an interaction take place? Repeat visits should ultimately be accelerated even further for an optimal user experience, and basic functions should be maintained even in the event of network failure or in a dead zone, i.e. offline.<\/p>\n<\/div>
- <\/i><\/span>Time to paint (FP, FCP, FMP, LCP)<\/div><\/li>
- <\/i><\/span>Time to interactive<\/div><\/li>
- <\/i><\/span>\n
Responsive<\/p>\n<\/div><\/li>
- <\/i><\/span>Bundle size<\/div><\/li>
- <\/i><\/span>Performance<\/div><\/li>
- <\/i><\/span>SEO, indexability<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
i18n & l10n, a11y<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Offline Mode<\/p>\n<\/div><\/li>
- <\/i><\/span>Event Management<\/div><\/li>
- <\/i><\/span>Events<\/div><\/li>
- <\/i><\/span>Hotel industry<\/div><\/li>
- <\/i><\/span>Hospitality<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>The application was implemented as a Progressive Web Application (PWA) based on the latest frontend technologies: Angular 9 Universal with Server Side Rendering (SSR) and ServiceWorker. This means that the application is rendered in advance by the server as a static HTML page and delivered and displayed to the visitor, while during the following seconds it is rehydrated under the hand – imperceptibly for the visitor – i.e. seamlessly replaced by the dynamic application. The first contact sees – even in poor mobile network conditions – the complete website within about 2 seconds. As soon as the visitor has visually captured the page a few seconds later and starts interacting, the application is launched and ready to go. This conveys an impression of immediacy that welcomes the user and holds his attention. Any further navigation of the visitor with the application is then handled by the ServiceWorker on the client side, or additional components or resources are loaded as needed. An integration of Ionic 5 as well as Capacitor or Cordova was considered, but discarded as not necessary based on the specific project requirements and the existing nativeness given by the PWA properties.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
100%<\/h2><\/div><\/div>Native-like User Experience<\/div><\/div><\/div><\/i><\/span><\/div>100% <\/h2><\/div><\/div>Device-independent and high-performance<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>One of the major challenges in developing responsive, dynamic, feature-rich web applications with high user interaction is load-time performance. This means accelerating the “time to paint” and “time to interactive” and thus successfully implementing initial contacts in particular. When a user first views a website, every second determines its success – depending on your target audience, every second 10% of visitors lose interest in your application and bounce. Under real network conditions, how long does it take for the visitor to see the application in the browser – and when can an interaction take place? Repeat visits should ultimately be accelerated even further for an optimal user experience, and basic functions should be maintained even in the event of network failure or in a dead zone, i.e. offline.<\/p>\n<\/div>
- <\/i><\/span>Time to paint (FP, FCP, FMP, LCP)<\/div><\/li>
- <\/i><\/span>Time to interactive<\/div><\/li>
- <\/i><\/span>\n
Responsive<\/p>\n<\/div><\/li>
- <\/i><\/span>Bundle size<\/div><\/li>
- <\/i><\/span>Performance<\/div><\/li>
- <\/i><\/span>SEO, indexability<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
i18n & l10n, a11y<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Offline Mode<\/p>\n<\/div><\/li>
- <\/i><\/span>Event Management<\/div><\/li>
- <\/i><\/span>Events<\/div><\/li>
- <\/i><\/span>Hotel industry<\/div><\/li>
- <\/i><\/span>Hospitality<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>The application was implemented as a Progressive Web Application (PWA) based on the latest frontend technologies: Angular 9 Universal with Server Side Rendering (SSR) and ServiceWorker. This means that the application is rendered in advance by the server as a static HTML page and delivered and displayed to the visitor, while during the following seconds it is rehydrated under the hand – imperceptibly for the visitor – i.e. seamlessly replaced by the dynamic application. The first contact sees – even in poor mobile network conditions – the complete website within about 2 seconds. As soon as the visitor has visually captured the page a few seconds later and starts interacting, the application is launched and ready to go. This conveys an impression of immediacy that welcomes the user and holds his attention. Any further navigation of the visitor with the application is then handled by the ServiceWorker on the client side, or additional components or resources are loaded as needed. An integration of Ionic 5 as well as Capacitor or Cordova was considered, but discarded as not necessary based on the specific project requirements and the existing nativeness given by the PWA properties.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
100% <\/h2><\/div><\/div>Device-independent and high-performance<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>One of the major challenges in developing responsive, dynamic, feature-rich web applications with high user interaction is load-time performance. This means accelerating the “time to paint” and “time to interactive” and thus successfully implementing initial contacts in particular. When a user first views a website, every second determines its success – depending on your target audience, every second 10% of visitors lose interest in your application and bounce. Under real network conditions, how long does it take for the visitor to see the application in the browser – and when can an interaction take place? Repeat visits should ultimately be accelerated even further for an optimal user experience, and basic functions should be maintained even in the event of network failure or in a dead zone, i.e. offline.<\/p>\n<\/div>
- <\/i><\/span>Time to paint (FP, FCP, FMP, LCP)<\/div><\/li>
- <\/i><\/span>Time to interactive<\/div><\/li>
- <\/i><\/span>\n
Responsive<\/p>\n<\/div><\/li>
- <\/i><\/span>Bundle size<\/div><\/li>
- <\/i><\/span>Performance<\/div><\/li>
- <\/i><\/span>SEO, indexability<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
i18n & l10n, a11y<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Offline Mode<\/p>\n<\/div><\/li>
- <\/i><\/span>Event Management<\/div><\/li>
- <\/i><\/span>Events<\/div><\/li>
- <\/i><\/span>Hotel industry<\/div><\/li>
- <\/i><\/span>Hospitality<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>The application was implemented as a Progressive Web Application (PWA) based on the latest frontend technologies: Angular 9 Universal with Server Side Rendering (SSR) and ServiceWorker. This means that the application is rendered in advance by the server as a static HTML page and delivered and displayed to the visitor, while during the following seconds it is rehydrated under the hand – imperceptibly for the visitor – i.e. seamlessly replaced by the dynamic application. The first contact sees – even in poor mobile network conditions – the complete website within about 2 seconds. As soon as the visitor has visually captured the page a few seconds later and starts interacting, the application is launched and ready to go. This conveys an impression of immediacy that welcomes the user and holds his attention. Any further navigation of the visitor with the application is then handled by the ServiceWorker on the client side, or additional components or resources are loaded as needed. An integration of Ionic 5 as well as Capacitor or Cordova was considered, but discarded as not necessary based on the specific project requirements and the existing nativeness given by the PWA properties.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Challenge<\/h2>\n<\/div><\/div><\/div>One of the major challenges in developing responsive, dynamic, feature-rich web applications with high user interaction is load-time performance. This means accelerating the “time to paint” and “time to interactive” and thus successfully implementing initial contacts in particular. When a user first views a website, every second determines its success – depending on your target audience, every second 10% of visitors lose interest in your application and bounce. Under real network conditions, how long does it take for the visitor to see the application in the browser – and when can an interaction take place? Repeat visits should ultimately be accelerated even further for an optimal user experience, and basic functions should be maintained even in the event of network failure or in a dead zone, i.e. offline.<\/p>\n<\/div>
- <\/i><\/span>Time to paint (FP, FCP, FMP, LCP)<\/div><\/li>
- <\/i><\/span>Time to interactive<\/div><\/li>
- <\/i><\/span>\n
Responsive<\/p>\n<\/div><\/li>
- <\/i><\/span>Bundle size<\/div><\/li>
- <\/i><\/span>Performance<\/div><\/li>
- <\/i><\/span>SEO, indexability<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
i18n & l10n, a11y<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Offline Mode<\/p>\n<\/div><\/li>
- <\/i><\/span>Event Management<\/div><\/li>
- <\/i><\/span>Events<\/div><\/li>
- <\/i><\/span>Hotel industry<\/div><\/li>
- <\/i><\/span>Hospitality<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>The application was implemented as a Progressive Web Application (PWA) based on the latest frontend technologies: Angular 9 Universal with Server Side Rendering (SSR) and ServiceWorker. This means that the application is rendered in advance by the server as a static HTML page and delivered and displayed to the visitor, while during the following seconds it is rehydrated under the hand – imperceptibly for the visitor – i.e. seamlessly replaced by the dynamic application. The first contact sees – even in poor mobile network conditions – the complete website within about 2 seconds. As soon as the visitor has visually captured the page a few seconds later and starts interacting, the application is launched and ready to go. This conveys an impression of immediacy that welcomes the user and holds his attention. Any further navigation of the visitor with the application is then handled by the ServiceWorker on the client side, or additional components or resources are loaded as needed. An integration of Ionic 5 as well as Capacitor or Cordova was considered, but discarded as not necessary based on the specific project requirements and the existing nativeness given by the PWA properties.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
SSR<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Service Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
One of the major challenges in developing responsive, dynamic, feature-rich web applications with high user interaction is load-time performance. This means accelerating the “time to paint” and “time to interactive” and thus successfully implementing initial contacts in particular. When a user first views a website, every second determines its success – depending on your target audience, every second 10% of visitors lose interest in your application and bounce. Under real network conditions, how long does it take for the visitor to see the application in the browser – and when can an interaction take place? Repeat visits should ultimately be accelerated even further for an optimal user experience, and basic functions should be maintained even in the event of network failure or in a dead zone, i.e. offline.<\/p>\n<\/div>
- <\/i><\/span>Time to paint (FP, FCP, FMP, LCP)<\/div><\/li>
- <\/i><\/span>
Time to interactive<\/div><\/li>- <\/i><\/span>
\nResponsive<\/p>\n<\/div><\/li>
- <\/i><\/span>
Bundle size<\/div><\/li>- <\/i><\/span>
Performance<\/div><\/li>- <\/i><\/span>
SEO, indexability<\/div><\/li><\/ul><\/div><\/div>- <\/i><\/span>\n
i18n & l10n, a11y<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nOffline Mode<\/p>\n<\/div><\/li>
- <\/i><\/span>
Event Management<\/div><\/li>- <\/i><\/span>
Events<\/div><\/li>- <\/i><\/span>
Hotel industry<\/div><\/li>- <\/i><\/span>
Hospitality<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>Realization<\/h2>\n<\/div><\/div><\/div>
The application was implemented as a Progressive Web Application (PWA) based on the latest frontend technologies: Angular 9 Universal with Server Side Rendering (SSR) and ServiceWorker. This means that the application is rendered in advance by the server as a static HTML page and delivered and displayed to the visitor, while during the following seconds it is rehydrated under the hand – imperceptibly for the visitor – i.e. seamlessly replaced by the dynamic application. The first contact sees – even in poor mobile network conditions – the complete website within about 2 seconds. As soon as the visitor has visually captured the page a few seconds later and starts interacting, the application is launched and ready to go. This conveys an impression of immediacy that welcomes the user and holds his attention. Any further navigation of the visitor with the application is then handled by the ServiceWorker on the client side, or additional components or resources are loaded as needed. An integration of Ionic 5 as well as Capacitor or Cordova was considered, but discarded as not necessary based on the specific project requirements and the existing nativeness given by the PWA properties.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nSSR<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nService Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>\n
PWA<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nSSR<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nService Worker<\/p>\n<\/div><\/li><\/ul><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div> - <\/i><\/span>
- <\/i><\/span>
- <\/i><\/span>
- <\/i><\/span>