Taking the P out of PWA

"Building better content creation with wysiwyg fields and custom formatters" slides from #DrupalGov CBR 2016.

Onne platform helps small businesses to connect, engage and transact with several entities that are part of their routine life, without noise, and provide small businesses, organizations and entities access to a digital interface that helps them connect directly with their customers.

Chaos engineering takes the complexity of a distributed system and tests it holistically by simulating turbulent conditions and observing how the system responds and performs. The data collected helps you build more resilient applications. This talk will explain the basic principles of chaos engineering and how they can be applied to build applications that will let you sleep through the night. Arun Gupta

Salesforce is one of the largest software companies in the nation because it can be truly amazing, but the document does not recommend for or against its use.

Microservices are the hot new thing, but where did they come from, and where are they going? This keynote will take you through the many origins of microservices. In it I’ll share with you some of the surprising influences and prior art that have shaped what they have become. By understanding where microservices architectures have their roots, we can learn from the past and avoid making the same mistakes – and we can also start to see where microservices will be going next. This talk was delivered as the keynote at QCon Sao Paulo in 2015.

This document outlines several benefits that a business can gain from developing a mobile app, including improved communication through a structured interface, better privacy controls, complete control over the app experience, automated reminders for tasks, centralized documentation storage, reduced manual work through automation, and increased business efficiency. It encourages businesses to get a free mobile app developed on the Onne platform.

This document discusses progressive web apps (PWAs). It defines PWAs as applications that take advantage of new technologies to provide the best of mobile sites and native apps to users. PWAs are reliable, fast, and engaging. They work across all devices and platforms without installation. Core aspects of PWAs include application shells, web app manifests, and service workers. Major browsers support key PWAs features like caching, adding to home screens, and push notifications. Popular companies using PWAs include Flipkart, Paper Planes, and Housing. The document encourages building and migrating to PWAs.

– DIY tips and tricks on leveraging WordPress, the most popular Open Source CMS in the world. – Not a developer? You don’t need to be to build automation, features, and functionality with the tools we will discuss. – The future of automating your content and revenue with artificial intelligence. Brian Messenlehner, CEO, AppPresser

This document provides instructions for integrating the Warbler loyalty program with other apps using Zapier. It explains that Zapier allows Warbler to connect to over 500 other apps without custom integration. The steps include requesting access to Warbler on Zapier, creating a zap to trigger a Warbler action like awarding points when a new comment is posted on a Wordpress site, and mapping the zap fields to connect apps like Wordpress to Warbler. Common FAQs about Zapier apps, zaps and tasks are also addressed.

Techqueria Event January 30, 2020 https://events.techqueria.org/events/details/techqueria-san-francisco-bay-area-presents-engineering-mentorship-event-with-asana/#/

The document describes the key features and functionality of the Timefly mobile app. It allows users to connect their social media accounts and view content in one place, organized by an algorithm. Users can save, share, filter, and interact with content directly from the app. The app was developed with a flexible architecture to allow for future enhancements and integrations.

Note: This is an expanded (roughly 90min) form of my "Confusion in the land of the serverless". Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we’ve built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor’s new clothes? This talk will very brie y introduce serverless computing, but will then dive into some of the questions that aren’t always asked in conjunction with this technology. By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations.

This document discusses how to make websites mobile friendly. It outlines three types of mobile apps and two approaches for developing mobile versions of existing websites. Wrapping the existing website in a mobile skin allows for shorter development time but can result in bad user experience, while tailoring the content for mobile provides a better experience but takes longer. The document demonstrates a mobile-optimized website and discusses testing, libraries, statistics, and approaches like starting mobile-first and using PhoneGap. The key messages are that content and context are important for mobile, and not all websites need native apps to go mobile.

The document discusses the importance of website loading speed. It notes that 47% of users expect a website to load within 2 seconds and 40% will leave if it takes longer than 3 seconds. To improve speed, the document recommends optimizing images, removing unused code, using tools like page speed audits, and adopting Accelerated Mobile Pages (AMP). Compressing images can significantly reduce file sizes while maintaining quality. The overall message is that small optimizations that save 1 second at a time are important and images provide a quick win for improving load speeds.

Slides presented during our SLS.Zone October 2019 meetup. Find us at meetup.com/sls-zone-meetup! === SLS.Zone is community-focused learning on serverless technology made by developers for developers. Bought to you by Reason.co. Visit https://sls.zone for more info.

The fight is over. It’s not web apps versus native apps, it’s a mobile world, and we need both. Let me tell you a bit about my experience with connected native apps, and why they are essentials. More importantly, how they can work with web apps and web services in order to build truly awesome experiences.

Jochen Wunder's presentation "10 Mobile Startups with Xamarin" for February 2015's Berlin Mobile .NET User's Group.

PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.

A state of web talk, discussing how Web Components, Progressive Web Apps, and Web Assembly are turning the web into an application platform.

These added capabilities will likely move many application developers to the web, creating a third vibrant app ecosystem. Having an open web app ecosystem will make apps more accessible to users in emerging markets and make it easier for new device manufacturers and operating systems to enter the market.

Presented at Web Directions Code, Melbourne If you have a website—particularly one that generates revenue for your organization—you need a Progressive Web App. So where do you begin? How do you decide which features of a Progressive Web App make sense for your users? What tools can make the process easier (or harder)? In this practical session, Jason will guide you through the key design decisions you’ll need to make about your Progressive Web App and how those decisions impact the scope of your project. He'll also teach you how to avoid common pitfalls and help you take full advantage of Progressive Web App technology.

Ran Wahle discusses using micro frontends to integrate legacy code into a modern single page application (SPA) in a peaceful way. A demo is shown integrating three sample applications - one using jQuery, one using Angular 6, and one using Angular 5 and Firebase. Micro frontends allow each application to have its own URL routing and inner routing while reusing backend services. Wrapping applications as custom elements is also discussed as an alternative to iframes for less isolation while still maintaining independence. The talk concludes that micro frontends can help extend legacy code and blend applications together to achieve "world peace" between new and old approaches.

Transcript of a discussion on a new platform designed from the ground up specifically to define, manage, secure, and optimize the API underpinnings for so much of what drives today’s digital business.

What are Progressive Web Apps and should you build one? This presentation looks at the problems PWA is aiming to solve and shows you how to get started.

Progressive Web Apps aim to bring the benefits of native mobile apps to the web. They use newer web capabilities like app manifests and service workers to deliver app-like experiences through the browser. App manifests allow web apps to be installed on home screens and launched full screen like native apps. Service workers enable features like offline access and push notifications. Early adopters are seeing increased user engagement through Progressive Web Apps, with metrics like conversions and time spent improving. While browser support is still evolving, Progressive Web Apps provide a promising approach for delivering high-quality mobile experiences through the web.

It is easy to think what we have as developers is what people use and that lead us to make the web bloated.

This document discusses building a progressive web app for an educational system. It begins by explaining the limitations of native mobile apps and regular web browsing. Progressive web apps aim to provide the rich experience of native apps while avoiding downloads through the use of service workers, responsive design, and app-like interfaces. The document then reviews related work on improving the mobile web experience. It presents the architecture of progressive web apps, including the application shell model and role of service workers. Finally, it proposes a system architecture for a progressive web app for education and concludes that these apps reduce burdens on users compared to native apps or regular web browsing.

Alan Semenov, Development Lead at Enonic discusses progressive web aps and understanding the value from a business perspective on top of a dev perspective

apidays Australia 2023 - Platforms, Products, and People: The Power of APIs October 11 & 12, 2023 https://www.apidays.global/australia/ APIs Aren't Enough: Why SaaS Leaders Are Investing In IPaaS Tim Pettersen, Head of Developer Experience at Atlassian ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Keynote covering what Progressive Web Apps mean to the market and what issues of native apps they need to fix.

The document discusses the importance of context and experience in mobile interactions. It notes that experiences need to adapt to how audiences interact across multiple devices throughout the day. It also discusses how mobile apps provide deeper engagement than mobile web due to features like offline access, notifications, and sensors. However, developing high-quality mobile apps is challenging for companies due to the costs, technical skills required, and need to support many device types and platforms. The document promotes Adobe solutions like AEM Mobile, Analytics for Mobile Apps, and Target for Mobile Apps to help companies unlock content for mobile, create business critical apps, measure app performance, and personalize the app experience.

In the coming age of AI and autonomous everything, how do you trust in the system, it’s accuracy, its precision of the decisions it will make for you to keep you and your family safe? This presentation focuses on how brands will now compete on data and data services head to head - what makes one better than the other and how would you decide who to trust?

As technology continues to disrupt every industry, mobile applications are increasingly becoming a primary way to interact with customers. Mobile application test automation tools and frameworks are far from being as mature as web test automation tools. The mobile test automation space is much more complex than web because of the number of devices that follow different standards. Simulators and emulators partially address this mobile diversity, however, to feel confident releasing an application to market, a deep understanding of what libraries, tools, and frameworks are available and how to best apply them is required. Join Pradeep as he presents information on how to tackle mobile test automation using tools such as appium and calabash, what to consider between Android and Iphone, how to select the right testing framework, the pro’s and con’s of open source vs. commercial mobile testing tools and the considerations for image based identification vs. object based identification approaches.

Progressive Web Apps (PWAs) are websites that are built using newer web application development techniques to provide an app-like experience to users. PWAs can be installed on the home screen, work offline, receive push notifications, and have app-like interactions. The document discusses how PWA provides a better user experience than traditional websites by making websites feel like native mobile applications while retaining the benefits of the web. It also discusses how travel website Trivago implemented PWAs to increase their market reach, conversion rates, and growth.

This document discusses the future of web apps and why mobile apps should eventually be replaced by web apps. It argues that web apps have improved and now can offer many of the same capabilities as mobile apps, such as working offline, push notifications, and adding to the home screen. New technologies like service workers and WebAssembly will continue enhancing web apps and make them even faster. While mobile apps still dominate usage today, the document predicts web apps will eventually surpass them as improvements are made and users realize the advantages of web apps over native mobile apps.

The document discusses microservices and how they differ from traditional monolithic applications. Some key points: - Microservices involve breaking an application into small, independent services that work together, each focused on a specific domain. This allows them to be developed and scaled independently. - In contrast, monolithic applications have all functionality locked together, making them slow to develop and scale. - Microservices help applications evolve more easily over time by allowing individual services to be updated independently. - The cloud further enables microservices by making it easier to publish and update applications continuously.

At Mobilize Dublin's January meetup, I shared some of the work we're doing at Intercom to help our customers to give their app users an amazing onboarding experience. I talked about how we explored the problem, decided on a solution, and shared a sneak peak at what we're building right now.

We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.

This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.

This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.

JavaScript is a bigger world than a language these days. Time to take stock and find happiness in that world.

This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.

The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.

This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.

The document provides five ways for JavaScript developers to be happier: 1) Concentrate on the present and focus on creating rather than worrying about the past or future. 2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features. 3) Make mistakes less likely by using linters to catch errors as you code. 4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions. 5) Give back to others in the community by being helpful rather than causing drama.

Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.

The document provides advice and encouragement for someone starting out with JavaScript development. It discusses how JavaScript can be used in many environments like browsers, apps, and servers. It recommends resources like MDN and tools like linting to help avoid mistakes. It emphasizes that this is an exciting time for JavaScript and advises setting priorities and standards, being involved in the community, and bringing new voices and perspectives.

Keynote at halfstackconf 2017 discussing the falsehood of the idea that in order to survive the automation evolution everybody needs to learn how to code. Machines can code, too.

Progressive Web Apps (PWAs) can provide app-like experiences through the web by making web content fast, reliable and engaging. While PWAs may not be necessary for all projects, they can help clean up and speed up current web-based projects. PWAs leverage new web capabilities like service workers to work offline, load fast, and improve the user experience without having to meet all the requirements of native apps.

This document discusses progressive web applications (PWAs) and their advantages over traditional native mobile applications. PWAs use modern web capabilities like Service Workers to deliver native-like experiences to users. Some key benefits of PWAs include their ability to work across platforms, have smaller file sizes for faster loading, support offline use, and provide simple update mechanisms compared to native apps. While PWAs do not have full access to device capabilities like native apps, they allow delivering app-like web content to users in a more accessible and reliable manner than traditional web pages.

Keynote at PNWPHP covering Machine Learning and How we should go about using it to build human interfaces.