Podcasts about browserstack

Explore how AI can automate quality assurance and testing for marketers and content teams.  QA experts Giselle Castro and Carlos Obaldia share how they compared two leading AI tools, Katalon and BrowserStack. Together, they discuss how these platforms help teams test faster, cover more ground and free up valuable time for creative and strategic work. Listeners will get a firsthand look at how Mod Op's QA team approached the comparison, the real challenges they tackled (like reducing manual testing and overcoming change resistance) and the measurable improvements they achieved.  Leader Generation is hosted by Tessa Burg and brought to you by Mod Op.  Contributors: Giselle Castro, Quality Assurance & Authoring (QAA) Carlos Obaldia, Senior Quality Assurance & Compliance Assurance (QA & CA) Guest Host Patty Parobek: As Vice President of AI Transformation, Patty leads Mod Op's AI practice group, spearheading initiatives to maximize the value and scalability of AI-enabled solutions. Patty collaborates with the executive team to revolutionize creative, advertising and marketing projects for clients, while ensuring responsible AI practices. She also oversees AI training programs, identifies high-value AI use cases and measures implementation impact, providing essential feedback to Mod Op's AI Council for continuous improvement. Patty can be reached on LinkedIn or at Patty.Parobek@ModOp.com.

In today's episode, we're diving into proactive observability and testing with our special guest, Anam Hira, cofounder of Reveal.ai. Anam, who also has experience working at Uber AI, shares an intriguing journey where he developed "Dragon Crawl," an innovative project aimed at tackling challenges Uber faced with its end-to-end testing across multiple cities. We explore how Dragon Crawl utilized LLMs to enhance testing reliability, making tests less flaky across varied UIs. Anam's journey didn't stop there. He co-founded Reveal, a platform that takes testing and observability to a new level by connecting end-to-end tests with telemetry data. This modern approach, termed proactive observability, allows for detecting bugs before they hit production, saving companies significant time and cost. Join us as we explore the principles of proactive observability, how Reveal leverages telemetry for seamless integration, and its impact on testing efficiency. Whether you're a startup or an enterprise, if you're keen to ship faster without sacrificing quality, this is an episode you won't want to miss!

In this episode of Revenue Insights, Adam Roberts talks with Raja Agrawal, VP of Sales at BrowserStack, about his journey from a rural Indian village to global sales leadership. They explore the evolution of B2B buying behaviors, managing a 100% remote sales team, the role of AI in sales operations, and the importance of cultural intelligence in global markets. With experience at SAP, Microsoft, and BrowserStack, Raja shares practical insights on fearless leadership, remote team management, and adapting to modern sales environments. Tune in for actionable strategies on driving global sales success.

In this episode of the Liquid Weekly podcast, host Karl Meisterheim and co-host Taylor Page welcome Paolo Vidale, founder and CEO of Hidden Gears, to discuss the intricacies of technical debt, quality assurance, and the evolution of Shopify development.Paolo shares his journey into development, emphasizing the importance of understanding technical debt both in-house and inherited from previous projects.The conversation delves into the philosophy of quality assurance, the challenges of JavaScript, and innovative approaches like inside-out re-theming to manage technical debt effectively. The episode concludes with insights on the latest changes in the Shopify ecosystem and personal picks from the hosts.Takeaways:• Technical debt is a crucial aspect of development that can accumulate over time.• Quality assurance should be viewed as a philosophy rather than just a task.• Diligence in testing involves anticipating user behavior and potential errors.• Inside-out re-theming allows for gradual improvements without complete overhauls.• JavaScript can introduce complexities, especially with conflicting libraries from apps.• Effective QA processes can prevent surprises and ensure a smoother development experience.• Collaboration with app developers can lead to better product outcomes.• Accessibility testing is an essential part of the QA process.• Understanding the implications of headless architecture is vital for successful implementation.• Using tools like Nacho Nacho can help manage SaaS subscriptions effectively.Timestamps:• 00:00 Introduction and Guest Introduction• 01:15 Paolo's Origin Story in Development• 07:40 Transitioning to Shopify and E-commerce• 09:59 Balancing Marketing and Development• 12:31 Quality Assurance in Development• 17:08 Understanding Quality Assurance• 21:14 Design QA vs. Development QA• 25:06 Accessibility and ADA Testing• 29:19 Navigating Complexity in Design and Accessibility• 30:10 Tools for Accessibility Testing• 33:18 Quality Assurance in Development• 34:32 Diligence and Destruction in QA Testing• 39:23 Understanding Technical Debt• 49:02 Inside-Out Re-theming for Technical Debt• 54:17 JavaScript Challenges and Solutions• 57:13 Dev Changelog and Picks of the WeekFind Paolo Online:• Website: https://www.hiddengears.com• Instagram: https://instagram.com/hiddengears• LinkedIn: https://www.linkedin.com/in/paolovidali/• Twitter(X): https://x.com/paolorobotResources:• ARIA DevTools: https://chromewebstore.google.com/detail/aria-devtools/dneemiigcbbgbdjlcdjjnianlikimpck?hl=en• Browserstack: https://www.browserstack.com/• Deque University: https://dequeuniversity.com/• WAVE: https://wave.webaim.org/• JAWS Inspect: https://www.tpgi.com/arc-platform/jaws-inspect/Dev Changelog:• Removing unnecessary RELEVANCE sort options: https://shopify.dev/changelog/removing-unnecessary-relevance-sort-options• Events and Origins in Store Credit Account Transactions: https://shopify.dev/changelog/events-and-origins-in-store-credit-account-transactions• Attribute Marketing Consent to Retail Locations: https://shopify.dev/changelog/track-the-retail-locations-where-your-customers-update-their-marketing-consentPicks of the Week:• Paolo: Saas and AI Marketplace (https://nachonacho.com/)• Karl: Logseq (https://logseq.com/)• Taylor: Wahl Clipper/Trimmer (https://amzn.to/4keu34q)Signup for Liquid Weekly Newsletter:Don't miss out on expert insights and tips—subscribe to Liquid Weekly for more content like this delivered right to your inbox each week: https://liquidweekly.com/

In this special episode, we're delving deep into the pressing challenges that automation engineers face daily and how our upcoming Automation Guild 2025 event is set to tackle these issues head-on. Don't miss it register for Automation Guild now! We'll discuss fresh survey data from over 200 automation professionals and explore pain points like test maintenance headaches, complex environments, AI integration, and much more. We also have some exciting sessions to preview, including techniques to scale tests without piling up technical debt, battling automation antipatterns, and leveraging AI for end-to-end testing. Plus, we'll touch on critical career advice and the ever-important aspect of team buy-in and collaboration. So get ready for an episode packed with practical insights and expert advice designed to help you succeed in your automation journey. Don't miss out on this one—it's going to be epic! Support the show and also check out this episodes sponsors BrowserStack testing solutions.  

Welcome to episode 280 of The Cloud Pod, where the forecast is always cloudy! This week Justin, Jonathan, Ryan, and Matthew are your hosts as we travel through the latest in cloud news. This week we're talking more about nuclear power, some additional major employee shakeups, Claude releases, plus saying RIP to CloudWatch Evidently and hello to Azure Cobalt VMs.   Titles we almost went with this week: The cloud providers are colluding on Nuclear Power I fear our AWS AI nightmare might get worse without Dr. Matt Wood. I'm a glow with excitement about nuclear cloud power Plainly no one else knew what “CloudWatch Evidently” did either We sing a Claude Sonnet about Nuclear Power Evidently, The Cloud Pod was always right Amazon goes nuclear while their AI VP goes AWOL A big thanks to this week's sponsor: We're sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You've come to the right place! Send us an email or hit us up on our slack channel for more info. AI Is Going Great – Or How ML Makes All It's Money   00:53 Introducing computer use, a new Claude 3.5 Sonnet, and Claude 3.5 Haiku Anthropic is announcing the upgraded Claude 3.5 Sonnet and a new Model Claude 3.5 Haiku.  Claude 3.5 Sonnet delivers across the board improvements over its predecessor, with particularly significant gains in coding — an area where it already leads the field (per anthropic).   Claude 3.5 Haiku interestingly matches the performance of Claude 3 Opus, the prior largest model, on many evaluations at the same cost and similar speed to the previous generation of Haiku.  Claude 3.5 Sonnet also includes a groundbreaking new capability in beta: Computer Use.   Available today as an API, developers can direct Claude to use computers the way people do – by looking at a screen, moving a cursor, clicking buttons and typing text.   Claude 3.5 is the first frontier AI model to offer this capability.  Anthropic warns the feature is still experimental – at times cumbersome and error-prone. As well as things that are effortless for a human are still difficult including scrolling, dragging or zooming.    The idea is to make Claude complete individual tasks, without always needing to leverage an API, like clicking in a GUI, or uploading a file from a computer.  These types of solutions are typically found in Build and Test like scenarios with tools such as Saucelabs or Browserstack.  To do this, Claude was built to perceive and interact with computer interfaces. You can use data from my computer to fill out this online form or check a spreadsheet, move the cursor to a web browser, navigate to the relevant web pages, select the data for the spreadsheet and so on.  3:06 Jonathan – “If you can take pictures of the screen, then it can identify where buttons and things are with

Accessibility is more than just a checkbox; it's become a civil right and a human need. Today, we'll explore how proper automation can elevate your accessibility testing to the next level. Check out our sponsors accessibility automation tool now: https://testguild.me/astack In today's episode, "Automation and Accessibility: Mutual, Not Exclusive," Crystal Preston-Watson, a senior digital accessibility analyst at Salesforce, joins us. This session was taken from our Automation Guild 2022 online event, where Crystal took us on an insightful journey, addressing higher-level questions and critical issues related to accessibility testing, specifically in automation. She also covers the essential considerations teams must consider before diving into accessibility automation. Learn about the different types of accessibility testing—manual, automation, and user acceptance—and discover why automated tools alone aren't enough to ensure proper accessibility. Listen in to discover the importance of experience with accessibility, the need for company-wide support and capacity, and best practices for combining manual and automated testing. By the way, to get on the waitlist for the lowest prices on tickets for the next Automation Guild event in February, go to automationguild.com now. And speaking of accessibility testing, I wanted to share an automated accessibility tool from this episode's sponsor, Browserstack.

In today's episode, we bring you an update from Nakul Aggarwal, co-founder and CTO of BrowserStack, a leading SaaS company from India, providing software app and browser testing infrastructure and products. Aggarwal talks about the rationale behind the acquisition of Bird Eats Bug, in Berlin, which BrowserStack announced yesterday. He also talks about evaluating building BrowserStack's own large language model, as the SaaS company progresses on its journey of transforming from a test infrastructure provider to a testing platform.

 In this session, Rudolf Groetz shares how Raiffeisen Bank International adapted its test automation strategy to incorporate a low-code approach. Discover how to transform from a traditional model to a more inclusive, agile approach. Try Low-code yourself now w/BrowserStack: https://testguild.me/lowcode Listen in to discover: The Challenges and motivations behind transitioning to a low-code strategy. Understand the steps to evaluate and select the appropriate low-code tools. See how non-technical users were empowered to participate in test automation. Observe the proof of concept results and how they impressed stakeholders. Hear the inspiring story of a biomedical intern discovering a passion for software development through this process.  

We discuss JSR, the new package registry from Deno, and whether it can compete with npm. Next, we talk about Parcel's new support for macros, which is a handy way to embed build-time logic into your code. After that we some get into some BrowserStack legal drama, and wrap up with some BREAKING NEWS about Apple, PWAs, and the EU. Drama!News:Paige - JSR - Deno's New JavaScript Package RegistryJack - Parcel v2.12 supports macrosTJ - Deque Systems Sues BrowserStack for Intellectual Property TheftJack - React 19's useOptimistic hookTJ - So what exactly did Apple break in the EU?BREAKING NEWS: Apple says iOS 17.4 won't remove Home Screen web apps in the EU after all What Makes Us Happy this Week:Paige - House of Ninjas series on NetflixJack - Dune 2 and Avatar The Last Airbender on NetflixTJ - Product launch at work Notecard LoRaWhite House urges developers to dump C and C++Thanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, reach out to us via email or Tweet us on X @front_end_fire.Blue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fire

Nozomi Ito is the co-founder and CEO of MagicPod, an AI no-code test automation platform supporting the development of high-speed, high-quality software. Using MagicPod, developers can easily automate most of their UI testing one step at a time, all without having to write any code. They can use the built-in device emulator for mobile app testing, or test on real-world devices they either own themselves or through integrations with SauceLabs, BrowserStack and HeadSpin. MagicPod raised a $2.4 million funding round from STRIVE and Angel Bridge.If you like our podcast, please don't forget to subscribe and support us on your favorite podcast players. We also would appreciate your feedback and rating to reach more people.We recently launched our new newsletter, Principles Friday, where I share one principle that can help you in your life or business, one thought-provoking question, and one call to action toward that principle. Please subscribe Here.It is Free and Short (2min).

On the 33rd episode of the Go Sokal Podcast, Frontend Developer Austin Calton describes his role in the website development process and how he uses a combination of languages and tools to make websites fast, effective across browsers and screens.Austin discusses core technologies, as well as programs like Adobe XD, FigJam, and Browserstack, and Chat GPT and no-code options like Squarespace and Webflow. We hope you enjoy!

Join us as we explore the journey of Alex Delic, Director at Code Development, from his earliest exposure to technology to his fascinating foray into coding. Listen in as we discuss his journey from playing with Raspberry Pi to coding professionally and his unexpected detour into archaeology during his university years. Unpack how Salesforce's investment in automated testing can help reduce the burden of manual regression testing and expand beyond just Salesforce applications. Alexander shares his insights on the challenges of UI testing and how MaxTAF can create reusable components for test scripts. In the world of mobile applications, we discuss the benefits and challenges of automated testing.  It's an episode filled with nostalgia, progress, and personal anecdotes you won't want to miss. Show Highlights: The concept of automated testing in application development. The role of technologies like Sauce Labs and BrowserStack in providing solutions for automated testing of mobile applications.  The importance of regression testing and the need for rigorous, structured testing methods to catch regressions.  The open-source technologies like Selenium, UTAM, and Playwright, used for automated testing.  The challenges and possible solutions for mobile testing. Links: Alex on LinkedIn: https://www.linkedin.com/in/alex-delic-32375874/ MaxTAF: https://www.maxtaf.com/  

Welcome to the TestGuild Automation Podcast! In this episode, host Joe Colantonio is joined by automation experts Lee Walsh and Michael Palotas to discuss the fascinating world of secure automation testing at scale, leveraging the power of Sbox. Michael, the Head of Product at Element 34, brings his wealth of experience from companies like eBay and Intel, while Lee, the Director of Customer Success at Element 34, adds his expertise from his time at BrowserStack.Throughout the conversation, the guests explore the importance of security and compliance in automation testing, the benefits and challenges of using different test tools like Selenium and Playwright, and the considerations enterprises must consider when choosing an automation solution. They also dive into the features and advantages of Sbox, Element 34's flagship product, including its ability to run tests within the customer's firewall, ensuring data privacy. Join us as we uncover the secrets to successful automation testing at scale and gain insights from industry leaders who have experienced firsthand challenges and triumphs. Let's dive in and discover the fantastic world of secure automation testing with Sbox! See a demo for yourself now: https://links.testguild.com/sbox

On this episode of TestGuild Automation Podcast, we have a special guest, David Burns, the W3C Browser Testing and Tools Working Group chairman and co-editor of the Web Driver Specification. In this episode, you will learn about the latest Nightwatchjs features. Also, you will gain insights into the significance of standardized technologies like JavaScript and why interoperability is vital for testing on different platforms. Additionally, the podcast provides exclusive information about Nightwatch and its features like component testing, plugins for visual regression testing, and API and unit testing capabilities. The episode also covers topics like BrowserStack, continuous integration, Selenium, Nightwatch Inspector, and Visual Studio Code. Tune in to learn more about the world of automation and how Nightwatch can help you achieve your automation goals.  

In this episode, I go over how to drive sales using inbound and outbound marketing for your small business. I also share several examples, resources, and tools you need to replicate my results and do it for your small business.Enjoy the full article this episode is for here: How to boost sales using inbound & outbound marketing for small businessesIn this episode, we will cover:The difference between inbound and outbound marketingWhat is inbound marketing?Benefits of inbound marketing.Challenges of inbound marketing.Examples of inbound marketing.Inbound marketing strategies.What is outbound marketing?Benefits of outbound marketing.Examples of outbound marketing.Outbound marketing strategies.Challenges of outbound marketing.How to use inbound and outbound marketing together.If you found this episode helpful, please tweet about it and tag me @Marketingbully_ . If you're ready to get started, I recommend downloading The Content Marketing Tool Kit and browsing my Freebie Library.Lastly, I did mention BrowserStack to test the responsiveness of your website and optimize it for mobile across different devices.Support the show

In Season 2 : Episode 1 of the Chief Future Officer podcast, Indus Khaitan, CEO of Quolum, interviews Nikhil Agrawal, Head of FP&A at BrowserStack. An IMI Graduate with more than 2 decades of Experience across GICs, E-Commerce, SaaS/PaaS, Tech product companies. Nikhil shares his journey in finance and how his consulting experience has given him a broader perspective on various industries. He also discusses his decision to join BrowserStack, a new-age tech business, to prepare for the future. As the commercial consciousness of BrowserStack, Nikhil describes his role in ensuring that decisions are commercially thought through, and how his team focuses on revenue and predictive analytics to achieve BrowserStack's financial targets. The discussion also covers the impact of the ongoing funding winter and the SaaS industry as a whole. For young finance professionals, Nikhil advises them to focus on adding value to their jobs and think about what value they can bring to the table. He emphasizes the importance of investing time in an organization to learn the business and find ways to add value. He also mentors young finance professionals, is quite active on LinkedIn and can be reached there for any questions related to finance career roles or problems. This podcast is a must-listen for anyone interested in finance and tech domain.

In this episode, you'll hear from five SeleniumConf Chicago 2023 speakers and/or project core committers about their upcoming talks, the reasons for their participation, and the benefits attendees can expect to gain from the conference. Additionally, our guests shed light on the Webdriver ecosystem - open-source projects that complement and add features and functionality to the browser automation capabilities that Selenium provides. They discuss the inaccuracies and misleading comparisons that pit Selenium against tools such as Cypress and Playwright. They also explain how using Selenium with Webdriver frameworks can help achieve parity with these tools while using real browsers. Join us as we hear from Corina Pip, QA Lead at Deloitte Digital; David Burns, Head of Open Source Program Office at BrowserStack; Noemi Ferrara, Software Dev Engineer II-TEST at Amazon Spain; Simon Stewart, Selenium Project Core Contributor and creator of WebDriver, and Marcus Merrell Vice President of Technology Strategy for Sauce Labs, . Tune in to learn more about browser automation, the Webdriver ecosystem, and how the community can work together to achieve better results.

Summary: Why is my app so buggy, and what can I do about it? Why can't developers just test their own code? Who's fault is it and who is to blame? Today’s guest is David Burns, Head of Open Source at BrowserStack, a popular platform for testing apps and websites in different browsers. David takes […]

In this video, we take a look at India's journey to 100 unicorns, from it's first ever startup unicorn in 2011, in the form of inMobi, to neobanking startup Open becoming 100th unicorn in 2022. The term 'unicorn' was created by American VC and entrepreneur Aileen Lee in 2013, she took all of the U.S.-based software companies that were started in or before 2003 and had achieved a valuation of $1 billion through public or private market investors, and put them in a club: the Unicorn Club. In India's case, it's unicorn journey started in 2011, when InMobi, a company that was founded in 2007, became a unicorn. Following this, Flipkart became a unicorn in 2012, Mu Sigma in 2014 and then Ola in 2014. Snapdeal also became a unicorn in 2014, but they have since exited from this club due to their valuation falling below $1 Billion. Companies like Quikr, Hike and Shopclues also fall in this category. Then we have companies who have been since acquired and also bags the question that should they be counted as unicorn today? Flipkart is an example here, which was acquired by Walmart. Then you have startups like Billdesk, which was bought by PayU, PhonePe getting acquired by Flipkart and BigBasket, which became a unicorn in 2019 and were acquired by Tata Digital in 2021. All this while, India's unicorn growth was pretty slow but steady till 2017, when Jio launched its 4G services, and this brought a mobile internet revolution in the country. From 1 unicorn in 2017, India saw 10 unicorns in 2018: B2C unicorns included Swiggy, OYO, BYJU'S, Policybazaar, Paytm Mall, and Phonepe, and B2B unicorns included Rivigo, Freshworks, Billdesk, and Udaan, which was the fastest company to become a unicorn at the time - it took them just 26 months. Then, in 2019, things slowed down a bit, with just 7 unicorns that year: in the B2C category were Ola Electric, Lenskart, Dream11, Delhivery, and BigBasket, and in the B2B category were Incertis and Druva. In 2020, COVID increased people's reliance upon the internet, and host of Indian e-commerce startups like Firstcry, Cars24, and Nykaa became unicorns. Facilitating these online payments resulted in fintech companies like Razorpay and Pine Labs also achieving unicorn status. B2C startups like Verse Innovation (Dailyhunt), ed-tech startup Unacademy, fintech startup Zerodha, and SaaS startup like Zenoti and Postman also became unicorn in the same year. 2020, was followed by an even bigger year in terms of unicorns in 2021, when 44 Indian companies became unicorns. This year saw 11 E-commerce startups (Spinny, OfBusiness, Moglix, Mensa, Meesho, Mamaearth, Licious, Infra.Market, Good Glam Group, GlobalBees, Droom), 11 Fintech startups (Zeta, Slice, Mobikwik, Groww, Digit, CRED, Coinswitch Kuber, CoinDCX, Chargebee, BharatPe and Acko) becoming unicorns. Then we have 5 enterprisetech and SaaS startups (Mindtickle, MapmyIndia, Gupshup, BrowserStack, Apna), 4 health startups (Cure.fit, Innovaccer, Pharmeasy, Pristyn Care), 4 consumer service startups (Blinkit, CarDekho, Rebel Foods, Urban Company), and 3 edtech startups (Eruditus, Vedantu and Upgrad) also becoming unicorns. Other 2021 unicorn categories include Media and Entertainment startups MPL and sharechat, Logistics startup Blackbuck, Traveltech startup Easemytrip , Real Estate startup Nobroker, and Manufacturing startup Zetwork. Talking about where where these startups coming from, they were all from tier 1 cities. Bangalore is leading this list with 39 unicorns, NCR region with 32 unicorns, mumbai with 16, Pune with 6, Chennai with 5 and Hyderabad with 2. Now we are halfway in 2022 and we have already produced and now it seems that by 2025, India will have upwards of 250 unicorns. So that will be exciting to watch and we will continue to track all of this in our upcoming episodes.

In this Episode, I (@Jivraj Singh Sachar) speak with Deven Parekh, Managing Director at Insight Partners. Insight Partners is a global software investment firm, which has one of the largest venture & private equity funds with over $90 Billion in Assets Under Management, having recently announced its new fund of $20Bn, headquartered in New York. Insight has invested in some of the most generation defining companies of our time across the globe including the likes of Twitter, Shopify, Checkout.com, Monday.com, Calm, Alibaba, Postman, BrowserStack, and many more. Deven is one of the veterans of the global investing ecosystem and has 22 years of partnering with phenomenal companies & founders. Through his illustrious career, Deven has partnered with companies such as Alibaba, Checkout.com, WeWork, Calm, Twitter, Slice, Chargebee, and many more. This was one of the most distinguished conversations from the Venture World on the podcast. I am certain that the next 50 minutes will give you a deep understanding of Institutionalised Global Investing as we know it. 1. (03:37) : The ideology of Insight Partners expanding their Investing across the globe (China, Israel, India, etc.) 2. (07:53) : How has Venture Investing evolved across the last 25 years? 3. (11:23) : Incredible Software Tech Investing Focus & Investing across stages from a Single Fund 4. (14:43) : Insight Partners on investing in other geographies without necessary physical presence 5. (16:39) : The Importance of the Sourcing Team & Scale Up Team (On-site) at Insight Partners 6. (19:29) : What is Deven's method on picking winners in Venture, especially considering that it is a sport of identifying Outliers? 7. (23:55) : What do some of the most successful founders radiate in terms of energy and in terms of key traits? 8. (27:29) : How does an experienced VC not let experience become a bottleneck? 9. (31:39) : How does Deven scale experience at the fund level? 10. (35:11) : Decoding Deven's intellectual curiosity across the last 22+ years and more! 11. (37:31) : Understanding the global investing outlook for the Indian Ecosystem from Deven's perspective! 12. (42:18) : How has Deven scaled over the years through his journey of being one of the most phenomenal Venture Investors of our team? 13. (46:09) : What is Balance and How is it different for everyone? 14. (49:09) : How does Relationship Building work in Venture? 15. (52:22) : Conclusion About our sponsor! Hope you liked the 90th Episode on the Indian Silicon Valley Podcast - Institutionalised Investing across the Globe That was it from this Episode, thanks again for tuning in! :) If you liked the episode, do share with your friends or drop us a quick review! Also, do follow us on social media to stay updated with all new episodes: Twitter: https://twitter.com/isv_podcast LinkedIn: https://www.linkedin.com/company/indian-silicon-valley-podcast/ Instagram: https://www.instagram.com/indiansiliconvalleypodcast/ Gallery of all Episodes: https://airtable.com/shrTOFf1z5UT0q9p8 You can also subscribe to the YouTube Channel of the Podcast : https://www.youtube.com/c/IndianSiliconValley/ "If you never try, you never know" Stay Tuned, Keep Building.

In this podcast episode, I welcome David Burns, Head of OSPO at BrowserStack, Chair person for the W3C Browser Testing and Tools Working Group, core contributor on the Selenium Open Source Project. We talk about the past, present and future of browser testing, how to eradicate flaky tests and why it's important to invest more effort into testing pyramid from the very beginning.Key points:David Burns on browser testingWebDriver BiDi specificationHow flaky tests are bornHow to start new or migrate existing projectsTesting pyramid and how tools support it (or do they?)Going BiDirectional with testingListen to the full conversation or read the edited transcript.You can also get Semaphore Uncut on Apple Podcasts, Spotify, Google Podcasts, Stitcher, and more.Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

In this Episode, I (@Jivraj Singh Sachar) speak with Prashanth Prakash, Partner at Accel India. Accel Partners India is one of the most accomplished institutional venture investors of our ecosystem. Accel has funded ground-breaking Indian ventures including the likes of BookMyShow, MuSigma, Flipkart, Freshworks, Swiggy, BrowserStack, Moglix, Urban Company! Through the episode we discuss - 1. (2:14) : The Accel Ideology of Investing ~ Having a Prepared Mind! 2. (05:05) : The Freshworks Deal for Accel

In today's video, we take a look at 10 tools that every startup founder needs to know about while building their business. BrowserStack: BrowserStack is a cloud-based app and website testing platform that it enables you to test your website or app on more than 3,000 physical desktop browsers, operating systems, and mobile devices via the cloud, so that you can make sure your platform is functioning smoothly for all of your users. BrowserStack is currently being used by more than 50,000 customers across the world. Taskade: Taskade is a real-time organization and collaboration platform for remote teams that essentially provides a unified workspace where you can communicate with your team, collaborate, and coordinate on projects. Taskade is minimalistic, simple, and intuitive - you can jump in and start getting things done faster and smarter, right away. Chargebee: Chargebee is a SaaS-based subscription and billing management tool that helps SaaSpreneurs to create customised subscription plans based on the size of their customer-base, and also takes care of international payments for them too, through partnerships with payment gateways in various countries. Calendly: Calendly is super useful if you're someone who has a lot of meetings or appointments. All you have to do is sync your Google calendar with Calendly so that it can access your schedule, set the days and times of the week you're available for meetings, and you're done. When someone wants to meet with you, you just send them your Calendly link, and they can pick the time that works best for them. Dyte: Dyte is an Indian audio & video software development kit provider. Basically, what Dyte allows you to do is create branded, customised live video and audio for your startup. Darwinbox: Darwinbox is an all-in-one HR management software that takes care of everything from hiring and recruitment to onboarding to performance management to managing their payroll. It gives you a complete overview of your organisation's workforce and solutions to track and manage everything from their salaries to giving timely feedbacks to evaluating their progress and performance. Square Space: Square Space is a website builder platform that offers a no-code solution where you can pick from thousands of website templates, and then use the platform's in-built customisation tools to make the website fit your startup. Square Space also has integrations with hundreds of different platforms to set up things like payments, marketing tools, schedule appointments, and social media integrations. MailChimp: MailChimp is an all-in-one email marketing tool that lets you create your own automated email campaigns from a single platform. They've got hundreds of email templates for things like a newsletter sign up, a website sign up, sending a discount code to a customer on their birthday, or reminding them to buy an item that they left in their cart but didn't purchase. Slack: Slack is an all-in-one business communications app that facilitates the setup of multiple communications channels for different teams across a startup or large company. You could have a marketing channel, a sales channel, a product development channel, all under the roof of one organisation, which means that teams can focus on having the conversations that matter within their department, but if they need to collaborate with other departments or drop into a channel to see what's going on, they can do that. Canva: Canva is a graphic design app for people who aren't great at using professional designing tools like Adobe Illustrator or Adobe Photoshop. By using Canva, anyone can design stuff using their thousands of templates without hiring professional graphic designers.

Esta semana pomos as contas em dia: gestão de contas no Percy e como mitigar ataques de enumeração de contas. Falamos também da ferramenta de lançamento de novas versões de Ember.js.Segue-nos no Twitter e junta-te ao nosso SlackLinks:Gestão de contas no Percy:BrowserStackPercyBrowserStack compra Percy - 2020testes de snapshot em Jest (React)"subaddressing" em endereços de emailMitigação de ataques de enumeração de contas:AlumniEIDevise para RailsUsername enumeration and the impact on anonymityPasswordless authenticationPassword managerTiming attacksVulnerabilidade do lobste.rs na recuperação de senhaFerramenta de lançamento de novas versões Ember.js:tool-new-release"Separating modules into different files"Ferramenta de extração de informação de ROMs de pokémonDo-nothing scripting: the key to gradual automationstructoptLivro "Rust for Rustaceans"O Conversas em Código é da autoria do Hugo Peixoto e de Ricardo Mendes

With the onset of the COVID-19 pandemic, a lot of companies stopped in their tracks and had to rethink everything. Others, however, hit the gas pedal. What exactly do you do when you're in the process of scaling fast and a pandemic strikes? In this episode, Mark Rudden – Director of EMEA Sales at BrowserStack – answers that question.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Last fortnight, BrowserStack raised $200M, at a valuation of $4Bn, making it India's most valuable SaaS startup. Join us for a behind-the-scenes peek at the A Junior VC piece - AJVC Unfiltered 28: Can BrowserStack be the World's Software Tester? For more details - https://ajuniorvc.com/browserstack-saas-unicorn-bootstrapped-testing-app-browser-india-startup/

#10 Wakefit: Founded by Chaitanya Ramalingegowda and Ankit Garg in 2015, Wakefit started selling mattresses online and were already making a profit within six months of operations. Today, this D2C mattress startup is selling 1,500 mattresses to their 500,000 customers every day – raking in a revenue of $26.5 million and making a profit of $1.3 million in FY20. #9 Lenskart: Founded by Peyush Bansal in 2010, Lenskart offers an omnichannel platform for selling eyewear and lenses through their online platform and offline stores. The company has been investing heavily in setting up new physical stores – taking the number of offline stores to over 750. This is why the startup took a decade to reach profitability. In FY20, Lenskart made a revenue of $130 million with a profit of $2.4 million. #8 Cashfree: Cashfree is a digital payments gateway platform that offers more than 100 payment methods to over 50,000 businesses around the world with a team of just 130 employees. Their ability to stay lean has not only enabled them to scale but also remain profitable from the get-go. Their profit increased 14X from just $190,000 in FY18 to $2.6 million in FY20. #7 BrowserStack: India's most valuable SaaS startup BrowserStack enables developers to test their apps remotely using their cross-browser testing platform that has more than 2,000 devices and is being used by over 50,000 businesses across the world. The company has been profitable since day one. In FY20, BrowserStack raked in a profit of $3.8 million. #6 Aye Finance: SME lending startup Aye Finance has been profitable for the last three consecutive years and has disbursed loans worth more than $538 million to more than 200,000 small businesses. Aye Finance's profits have increased to $5.3 million in FY20. #5 Lendingkart: Founded in 2014, Lendingkart has disbursed loans worth $741 million to more than 100,000 small businesses. This fintech startup first achieved profitability in FY19 and their profits stand at $5.6 million in FY20. #4 OfBusiness: B2B e-commerce and lending startup OfBusiness uses purchase financing – providing businesses with a loan that they can use to purchase raw materials from their e-commerce platform. Once their profits from the interest started coming in, OfBusiness started making money and they are now on their way to becoming a unicorn. Their profits jumped 73X from just $150,000 in FY18 to a healthy $80 million in FY20. #3 CarTrade: Founded in 2009, CarTrade is the only profitable online used car marketplace. This decade-old startup has already filed for an IPO and is expected to hit the stock markets soon. The company significantly decreased its losses from $20 million in FY16 to just $2 million in FY17. They first turned profitable in FY18 and they did this through internal restructuring, key acquisitions and cost-cutting measures. Today (FY20), they are making a healthy profit of $11.5 million. #2 Boat Lifestyle: Indian consumer technology startup Boat started in 2016 by selling charging cables and were able to hit profitability within the first year. Next, they launched more products like earphones, headphones and smartwatches with quality and affordability in mind to target value-minded Indian consumers. This strategy only accelerated their growth. Boat's profit's increased by 30X from just $225,000 to $6.6 million in FY20. #1 Zerodha: India's largest stockbroking platform Zerodha has managed to change the entire stock trading industry single-handedly and they did it without even raising any external funding or marketing their product. Today, Zerodha charges just Rs 20 (or 0.03% as commission – whichever is lower) from their customer for every intraday trade. Thanks to that, Zerodha earned a solid $135 million in profits in FY21.

Welcome to another episode of The Startup Operator Roundup, where Roshan Cariappa and Gunjan Saha discuss -

This week in Indian Startup News, India's largest crypto trading platform WazirX gets tangled in a money-laundering probe, India's first official drone delivery trial begins, PhonePe's acquisition deal with Indus OS turns into a lawsuit, CultFit acquires Tread to foray into at-home fitness hardware and InMobi's Glance acquires Shop101 to launch live commerce. In funding news, Byju's raises $350 million to become India's most valuable startup, BrowserStack raises $200 million to become India's most valuable SaaS startup, Vianai Systems raises $140 million, Apna.co raises $70 million and FamPay raises $38 million. India's largest crypto trading platform WazirX gets tangled in a money-laundering probe: India's financial investigation agency Enforcement Directorate (ED) has issued a notice to WazirX and its directors Nischal Shetty and Sameer Mhatre – seeking an explanation for crypto transactions worth $400 million. ED has accused them of not carrying out proper KYC which led to Chinese nationals operating illegal online betting apps to launder money through their platform by buying cryptocurrencies. India's first official drone delivery trial begins: A consortium led by Throttle Aerospace Systems became the first to officially start drone delivery trials to deliver medicines in partnership with Narayana Health. PhonePe's acquisition deal with Indus OS turns into a lawsuit: PhonePe was trying to acquire Indus OS for $60 million to strengthen their mini app store Switch but the deal soon turned into a lawsuit between PhonePe and Indus OS's investor Affle on the difference of valuations. PhonePe has also filed a complaint against another Indus OS investor Ventureast to Sebi for deceiving them and side dealing with Affle to scuttle the deal. CultFit acquires Tread to foray into at-home fitness hardware: Health and fitness startup CultFit has acquired at-home smart fitness bike maker Tread to give their customers a more comprehensive fitness and training experience at home. InMobi's Glance acquires Shop101 to launch live commerce: Glance has acquired social e-ecommerce startup Shop101. The startup will be leveraging its short video platform Roposo along with Shop101's e-commerce capabilities to launch celebrity and influencer-led live commerce on their platform. Byju's raises $350 million to become India's most valuable startup: Edtech giant Byju's has raised $350 million in fresh capital from UBS Group, Zoom founder Eric Yuan, Abu Dhabi's ADQ, Blackstone and Phoenix Rising at a $16.5 billion valuation – leaving behind Paytm to make it India's most valuable startup. BrowserStack raises $200 million - India's most valuable SaaS startup: App and website testing platform BrowserStack has raised $200 million led by BOND Capital at a $4 billion valuation to accelerate their growth via acquisitions. Vianai Systems raises $140 million: Infosys' former CEO Vishal Sikka's new venture Vianai Systems has raised $140 million in fresh capital in a round led by SoftBank's Vision Fund 2. Apna.co raises $70 million: Professional networking and job search platform for blue-collar workers Apna has raised $70 million in a round led by Insight Partners and Tiger Global Management at a valuation of $570 million. FamPay raises $38 million: Fintech startup FamPay has raised $38 million in a round led by Elevation Capital to build India's first neobank for teenagers. They will use the capital to expand their user base and add more products to their suite.

BrowserStack, a software testing platform, has announced its Series B fundraise of $200 million from BOND, at a valuation of $4 billion, making it the highest for any Indian SaaS unicorn. Insight Partners and existing investor Accel participated in the funding. The Series B fundraising makes BrowserStack India's second SaaS unicorn this year, after Chargebee, which attained the tag in April. In its press release, BrowserStack stated that the funding would be used to support its acquisitions, expand its product offerings, and scale growth. Miami-based Novo, a digital banking platform for small businesses, has raised $40.7 million in a Valar Ventures-led Series A funding round. Other investors – Crosslink Capital, Rainfall Ventures, Red Sea Ventures, and BoxGroup – participated in the funding round, the company said in its press release. The company stated that it would use the proceeds from the investment to introduce new capabilities for assisting small businesses save time and money by optimizing their cash flow.Tel Aviv-based Bringg, a cloud platform that helps retailers and logistics providers in last-mile delivery operations, has announced its Series E fundraise worth $100 million, led by Insight Partners at a valuation of $1 billion. The Series E fundraising grants it the unicorn status, making it the first company in last-mile delivery and fulfillment cloud technology to attain the status, its press release said.Vianai Systems, an AI startup, has announced that it has raised $140 million in a Series B funding round led by SoftBank Vision Fund 2. The Palo Alto-headquartered startup said that many industry stalwarts participated in this round. The new round takes the total to at least $190 million.   20 minute VC podcaster Harry Stebbings has raised funding for 20VC. The current raise represents a 15-fold increase over the $8.3 million initial funds, which was launched less than a year ago. Mr. Stebbings' early-stage fund, 20VC Early, will invest $250,000 to $750,000, while his growth-stage fund, 20VC Explorer, will invest $1 million to $5 million.  DuckDuckGo, an online privacy startup, has claimed a $100M revenue increase. This growth is attributed to secondary investment from existing and new investors. In the last year, its apps have been downloaded over 50 million times. The company intends to extend its operations throughout Europe and other parts of the world.Copenhagen-based Templafy, a B2B business document creation SaaS platform, has raised $60 million in its Series D funding round led by Blue Cloud Ventures. Existing investors – Insight Partners, Seed Capital, Dawn Capital, and Damgaard Company – had participated in the round, reports state.Gloat, a talent marketplace platform helping enterprises worldwide harness talent, has announced its Series C fundraise worth $57 million, led by Accel. Existing investors – Eight Roads Ventures, Intel Capital, Magma Venture Partners, and PICO Partners-participated in the funding round. Trigo, a retail checkout system developer, has raised $10M (the exact amount is undisclosed). Its total funding has crossed $100M with this funding, and it looks to partner with Germany's REWE Group to help them set up a ‘grab and go' shopping experience for its new store in Cologne.Brella, a hybrid event platform, has raised $10 million in a Series A funding round led by Connected Capital. The platform, previously utilized as an offline networking tool, shifted from live events to a virtual event platform once the pandemic struck.Introhive, AI-powered sales, and revenue acceleration platform, has raised $100 million in a Series C funding round led by PSG, a growth equity firm. Other investors include Mavan Capital Partners, The Business Development Bank of Canada (BDC), and Evergreen Capital.

Microsoft's independent directors unanimously elected Satya Nadella to the role of board chair yesterday, expanding the CEO's influence in the company. Nadella, who has been CEO of Microsoft since 2014, is one of the most well-known Indian executives leading America's biggest technology companies. Also in this programme, Mumbai's BrowserStack is valued at $4 billion after BOND investment; and Lendingkart's Harshvardhan Lunia discusses his efforts to finance small businesses with more digital tech

Vikram's exceptional guest on the podcast today has worked for many years and is currently a partner at Accel, Shekhar Kirani. With over 25 years of experience in business and tech leadership roles across several startups and large companies in the US, Shekhar specializes in investing in early-stage software and mobile startups that help enterprises. During his extensive career, he has led investments in ANSR, BrowserStack, CareStack, Cogoport, FalconX, Freshworks, and Zenoti, and he also played a crucial role in the seed stage funding of Chargebee.Shekhar begins by sharing his secret to juggling different startup contexts, the roles he played before becoming an investor, and some of the many lessons he has learned over the years, including the importance of onboarding, understanding the customer first, and the traits he looks for in early-stage companies. He also provides some advice regarding dealing with early-stage ‘haziness' and a glimpse into his prediction framework, thoughts around social consciousness from startups and technologies, and the product he sees the greatest need these days. Gifted with intellect, experience, and eloquence, Shekhar Kirani's insights are precious and will both educate and inspire listeners here today.

In this episode of This Week in Health Tech we welcome our very own and close friend Wayne Che to talk about Health System and Mobile Apps - Management, Resources, Build vs Buy, Testing, Infrastructure, Security, Privacy, and more!This episode aligns well with the new digital product offering of Tido Inc. for the management of mobile and web apps for health systems. Wayne Che works in multiple roles, primarily as CTO of Sowingo Inc., and has tons of experience with the implementation of mobile apps.We get right into mobile development by starting the discussion on build vs buy.Vik comments that health systems main focus is improving patient outcomes and it does not make sense to assemble a development team in-house. Wayne agrees that you gain speed of execution and plus allows you to focus on the primary job of using IT for providing better care of patients.Jimmy asks what to look for in the development shop and Wayne thinks that you need to have a partner that understands requirements and helps to define requirements. Also, the shop should not only have development skills but it is also more important to have management skills to keep the app updated and continuously test to provide the best user experience.Vik comments that Tido Inc. launched a new digital package to help health systems manage apps and includes custom development of apps. It also includes test automation and maintenance. Wayne indicates that testing and maintenance is a key component otherwise with iOS or android updates app may stop working.Vik and Jimmy then dive into test automation and the importance of testing on actual real devices. This is where real device testing comes into play. Both Vik and Wayne recommend the selenium framework with real device cloud providers like Sauce Labs or BrowserStack.Testing helps provide the best user experience and it is so crucial for patients who may be already going through a lot and a frustrating app experience just adds to negative patient satisfaction.The group then discusses infrastructure for apps. There are many cloud providers and what is the best approach for health systems.Wayne comments that cloud providers do several things well including staying compliant with HIPAA and PHIPA. Vik comments that using the cloud has another benefit which is to reduce traffic from mobile devices directly into the health system network.The group then talks about using APIs for data sharing for mobile apps. Also with ONC's Cures Act, it is required that there are no more data silos, but most health systems should go beyond Cures Act for bidirectional data flow securely.Wayne comments that this is where health systems should look into hiring the expertise for API development and management and ensure security.Jimmy asks the question of why this urgency of APIs and mobile development now? Wayne and Vik respond that not only Cures Act but from providing the best user experience, health systems have to provide APIs and app support.Group then talks about the hybrid approach for mobile app development where you have some expertise in-house, maybe a product owner or architect but use an outside development company.Website: http://www.thisweekinhealthtech.comTwitter: @TWIHT1Tido Inc.: https://www.tidoinc.com/Wayne Che: Wayne CheSowingo Inc: https://sowingo.com/Music Provided by Soundstripe.comSupport the show (http://www.thisweekinhealthtech.com/)

Deze aflevering bespreken Rick en Michele het Atkinson hyper legible font, inspiratie website CoDrops en alles rondom browsers. Atkinson Hyper legible font: https://brailleinstitute.org/freefont CoDrops: https://tympanus.net/codrops/ Browserstack: https://www.browserstack.com/ Brave browser: https://brave.com/ Electron: https://www.electronjs.org/ The five best design links, every weekday: https://www.sidebar.io The Ranch: https://www.netflix.com/nl/title/80077977

In this episode of This Week in Health Tech we welcome our very own and close friend Wayne Che to talk about Health System and Mobile Apps - Management, Resources, Build vs Buy, Testing, Infrastructure, Security, Privacy, and more!This episode aligns well with the new digital product offering of Tido Inc. for the management of mobile and web apps for health systems. Wayne Che works in multiple roles, primarily as CTO of Sowingo Inc., and has tons of experience with the implementation of mobile apps.We get right into mobile development by starting the discussion on build vs buy. Vik comments that health systems main focus is improving patient outcomes and it does not make sense to assemble a development team in-house. Wayne agrees that you gain speed of execution and plus allows you to focus on the primary job of using IT for providing better care of patients. Jimmy asks what to look for in the development shop and Wayne thinks that you need to have a partner that understands requirements and helps to define requirements. Also, the shop should not only have development skills but it is also more important to have management skills to keep the app updated and continuously test to provide the best user experience. Vik comments that Tido Inc. launched a new digital package to help health systems manage apps and includes custom development of apps. It also includes test automation and maintenance. Wayne indicates that testing and maintenance is a key component otherwise with iOS or android updates app may stop working. Vik and Jimmy then dive into test automation and the importance of testing on actual real devices. This is where real device testing comes into play. Both Vik and Wayne recommend the selenium framework with real device cloud providers like Sauce Labs or BrowserStack. Testing helps provide the best user experience and it is so crucial for patients who may be already going through a lot and a frustrating app experience just adds to negative patient satisfaction. The group then discusses infrastructure for apps. There are many cloud providers and what is the best approach for health systems. Wayne comments that cloud providers do several things well including staying compliant with HIPAA and PHIPA. Vik comments that using the cloud has another benefit which is to reduce traffic from mobile devices directly into the health system network. The group then talks about using APIs for data sharing for mobile apps. Also with ONC's Cures Act, it is required that there are no more data silos, but most health systems should go beyond Cures Act for bidirectional data flow securely. Wayne comments that this is where health systems should look into hiring the expertise for API development and management and ensure security. Jimmy asks the question of why this urgency of APIs and mobile development now? Wayne and Vik respond that not only Cures Act but from providing the best user experience, health systems have to provide APIs and app support. Group then talks about the hybrid approach for mobile app development where you have some expertise in-house, maybe a product owner or architect but use an outside development company. Website: http://www.thisweekinhealthtech.comTwitter: @TWIHT1Tido Inc.: https://www.tidoinc.com/Wayne Che: Wayne CheSowingo Inc: https://sowingo.com/Music Provided by Soundstripe.comLinkedin:

What's the first thought that gets triggered when you hear a mention of Coimbatore? For me, it's always been the city's entrepreneurial spirit. Much before startups became a cool word to go around, Coimbatore's entrepreneurs have been busy creating enterprises, failing, learning and growing. It's called “the Manchester of South India” for a solid reason. So it was a delight to record this conversation with Ganesh Shankar, CEO of RFPIO and Saravana Kumar, co-founder of Kovai.co--the two entrepreneurs who hail from Coimbatore, and who are now working relentlessly to make the city a next-generation SaaS hub. What's even more heartening is to learn how India SaaS pioneer Zoho and poster child Freshworks are inspiring this new wave. “The confidence that they gave us (Zoho and Freshworks) is amazing because even we now have 15 of the Fortune 500 companies as customers. Both Zoho and Freshworks have delivered quality products globally from India, and that's the key motivation,” Ganesh tells me in this podcast. For a long time, Zoho remained an inspiration for a generation of SaaS startups founded by its former employees. Then came Freshworks; a complete breakaway from the Zoho's bootstrapped model, fast-growing and nourishing an amazing product-design culture. And while both Zoho and Freshworks continue to be the role models for most SaaS companies, it's amazing to watch the rise of another generation led by the likes of Postman and Browserstack. “What Freshworks has done to Chennai is what we want to do to Coimbatore because that spot is still available,” Saravana tells me in this podcast. Kovai.co now has its own campus in Coimbatore, built with an investment of over $1 million. Chargebee, co-founded by Krish Subramanian, is another inspiration for startups such as Kovai.co“They are coming in and proving that you can build world-class products and scale,” adds Saravana. Startups such as Kovai.co, which is at almost $10 million ARR, and RFPIO that counts Zoom, Microsoft and Adobe among its customers, are beginning to democratise the India SaaS story by looking beyond the traditional IT hubs of Chennai and Bengaluru. Listen to this podcast to learn from the entrepreneurial journeys of RFPIO and Kovai.co, and how the startups' founders, Ganesh and Saravana, are on a mission to make Coimbatore the next SaaS hub. 

In this episode, I chat all about CSS with my guest Mark Ryba, a senior developer at SmartBug Media who has over 6 years of front end development experience in the marketing space. In his current role he develops middleware microservices, websites and web applications. He’s also very passionate about using advanced CSS techniques to create great user experiences. ******************************* Questions Asked ******************************* Tell us about your background. Define CSS. Why is it called CSS? What's the difference between inline, in file and external CSS? What is the industry best practice when embedding versus external CSS? Can CSS be used for Mobile and iOT devices as well as web? Can CSS be used for animation? What's the difference between plain CSS and a CSS framework? Why do CSS Frameworks exist? What is a grid system in CSS? How does responsive design relate to CSS? What's the float layout? Tell us about Flexbox? Tell us about the Foundation CSS framework? Tell us about Tailwind. Which browser supports which framework? What is prefixing in CSS? What happens to CSS that is not supported by a specific browser in that browser? How do you debug CSS? How do you keep up with the latest in CSS? What do you love the most about CSS? What do you find most challenging with CSS? What would you like to see in CSS 4? ******************************* Reference Links ******************************* SmartBug Media (https://www.smartbugmedia.com/) Mark’s Twitter (https://twitter.com/markryba2nd) HubSpot (https://www.hubspot.com/) CodePen (https://codepen.io/) CSS-Tricks (https://css-tricks.com/) Bootstrap (https://getbootstrap.com/) CanI Use (https://caniuse.com/) BrowserStack (https://www.browserstack.com/)

In this episode, Ross and John speak to Mark Rudden, Head of EMEA Sales & Global Sales Operations at Browserstack. Mark has undertaken a massive project to scale out Browserstack's EMEA presence out of their Dublin office. BrowserStack is seeing massive growth as organisations continue to move their web and app testing infrastructures to the cloud. With a Series A of $50m in funding from Accel Ventures the future is very bright. Mark also shares with us his career journey, moving into SaaS and his journey into sales and operational leadership. Career Growth: Why having a miscellaneous start to your career is a great way to figure out what you're actually good at. How Salesforce was his Bachelor's Degree in SaaS. Why he favours chaos over politics. The three P's he uses to evaluate each SaaS company worth working for (Product, People, Progression) Leadership and Company Growth: How to be a ‘Servant Leader' and have a people-first approach. How to plan effectively for hiring in Hyper-Growth organisations. How do you decide on strategy for your EMEA markets? How does data determine your decision making - fail to plan, plan to fail! How do you keep up the learning curve and balance lead flow to your reps. Sales Philosophy: What do sales professionals actually control in the sales process Why getting an early 'No' is key. How do you make a connection with new hires when training remotely. When to slow down and when to speed up. Why does he recommend competitors? Balancing a ‘land and expand' strategy for perpetual value. Browserstack - what do they do and what value do they offer to engineering teams. Brought to you by sf-talent.com. --- Send in a voice message: https://anchor.fm/gloabl-tech-leaders/message

Darüber haben wir geplaudert: Leistung; Barometer; enkrateia (Activity tracker data analysis for Android and iOS); Google Street View verpixeln lassen; MyMail App und mail.ru; Yubico Yubikey; Security-Token; FIDO2; Windows Hello; Python FastAPI, Virtualenv, Pipenv, Anaconda; BrowserStack; NVD3; Webpack; Angular; Phoenix LiveView; Ruby Volt; Source Maps; Sass und SCSS; CSS-in-Vienna Meetup; Vue.js; Svelte; React; CodePen; Visual Studio Code; NoMachine; 5G Dinge; LoRaWAN; VoLTE; Feinstaub-Sensor; Android TV; Obsoleszenz; Chromebook; Linux Desktop; Remote Desktop; Intel Clear Linux; A gscheiter Rechner; #covfefe Gäste: Bernhard, Stefan, Ulrich

Spotify Link: https://open.spotify.com/show/1YQdnQ50mmenzWVA2MBsQy Apple Podcast: https://podcasts.apple.com/us/podcast/insights-podcast-series/id1364412685The several success stories of Zoho, Freshworks, Browserstack, Icertis who have all reached several hundred million dollars in ARR with most of their product built in India give proof points for the possibility to build large scale SaaS companies coming out of India.Unlike the 90s when software was a one-time sale, the subscription nature of SaaS pricing ensures that the interests of the customer and the software vendor are well aligned. Today, there are over a hundred thousand software companies serving over two thousand categories with over five hundred billion dollars spent on software purchases. The SaaS industry is just one hundred fifty to two hundred billion dollars, so there's another three hundred billion dollars of traditional on-prem software that needs to be replaced. Another opportunity exists in creating a product for the customers currently being served by custom software solutions built by the large IT services companies. At the same time, new industries are seeing digitization, creating more opportunities for building software. In terms of liquidity as well, SaaS as a sector offers significant options- from an active M&A market and active interest from venture capital and private equity to fund growth to several examples of companies going public. Krish ends by quoting Jason Lemkin, “In a SaaS business, once you cross $10M with good momentum, you basically become unkillable because of the recurring nature of the business”

In the first episode of 2020's #InsightsPodcast series, we take a look back to round up the learnings that 2019's series left us with.We kick-start 2020's #InsightsPodcast series with a special episode that offers a quick roundup of our 2019 podcasts and presents the top 12 highly recommended insights for entrepreneurs. Finding the right opportunity The bare essential task of identifying the right opportunity is something that every founding team must go through. 1.Farid Ahsan of Sharechat shares how he and his co-founders went about discovering the idea. “We started observing why people were making WhatsApp groups and sharing content on them.” 2.Ritesh Arora of Browserstack shares the importance of thinking global from early on, helping expand the opportunity set for the startup. 3.Kunal Shah of Cred shares his framework on how startups can validate whether their idea is creating a delta change in consumer behaviour and emphasises the importance of picking a market opportunity with good tailwinds. “Great product-market fits even with mediocre founders create a lot of value while terrible product-market fits with great founders can never create value. Fighting headwinds only burns fuel.” Building a team and culture to go after that idea The team forms the building block of any organisation and is an integral contributor to the success of a startup. A good culture keeps the team motivated to keep going after the problem. 4.Naveen Tewari of Inmobi talks about the importance of having a co-founder in the roller-coaster of a journey that entrepreneurship comprises. “Most of the moments in the journey are low moments. The co-founder's role is to bring you out of these low moments that you're in and vice versa.” 5.Binny Bansal of Flipkart shares about the importance of being willing to ‘let go' and empowering your team. “We realised that only way to scale the company was to hire people like us, to do the things that we do - there were going to be hundreds of things to do and we would need hundreds of people would need to work like we work, every day.” 6.Girish Mathrubootham of Freshworks talks about focusing about culture and building a work environment that motivates and inspires the team. “Anybody can create a happy work environment, but the real happiness is when people really feel that they're playing to their strengths, the job is tapping their potential and giving them an opportunity to learn, and that they have managers who they see as role models.” Raising money and building a sustainable company With a boundless vision comes the need to find the right support, and finding the right investor can really help a startup. 7.Harsh Jain of Dream11 talks about the advantage of meeting investors ahead of fundraising. “Meet VCs six months or a year before raising money and get honest, open feedback. When the journey and progress is shared with VCs, they're much more vested.” 8. Deep Kalra of Makemytrip talks about the importance of unit economics and scaling sustainably. “Irrespective of the kind of business, you should not be losing money on a variable cost basis.” Key lessons for founders' growth In the greater scheme of the startup journey, the founder's individual self often gets ignored. Here are some key insights on keeping a founder's growth on track. 9. Shradha Sharma of YourStory talks about the founder's growth journey being more internal and how entrepreneurship is a journey of patience and perseverance. “You have to internally reflect very deeply on what you want.” 10. Nandan Nilekani of Infosys and the man behind the Aadhaar programme talks about the importance of being execution-focused. 11. Ritesh Agarwal of Oyo talks about the importance of perseverance. 12. Dheeraj Pandey of Nutanix shares his valuable insights on balancing family life along with running a startup.

Dedicamos este episodio a hablar con Álvaro Trigo de fullPage.js, que acumula una experiencia notable en desarrollo y mantenimiento de proyectos de código abierto a tiempo completo. Con Álvaro hablamos de los dos tipos de pull requests en el soporte de proyectos open source y qué hacer para no saturarse, los retos de cobrar por un componente frontend de JavaScript y los beneficios de crear un sistema de extensiones limitado por clave de licencia. También hablamos sobre desarrollar en móvil cuando no tienes acceso a la consola de JavaScript en ciertos navegadores, cómo hacer un proyecto open source fiable y mantenido en el tiempo y por qué Álvaro nunca ha usado marketplaces y prefiere anunciar en su propia página.Te recomendamos:Perfiles sociales de Álvaro:- Twitter: https://twitter.com/IMAC2- GitHub: https://github.com/alvarotrigoEnlaces de interés:- fullPage: https://alvarotrigo.com/fullPage/- Q&A en el blog de BrowserStack: https://www.browserstack.com/blog/open-source-spotlight-fullpage-js-alvaro-trigo/- Álvaro Trigo en YouTube: https://www.youtube.com/channel/UCTDd08U8qLiFrWr608Mh_3A- Cómo consigue Álvaro gestionar fullPage y consigue hacer empresa con este proyecto open source: https://www.zentao.pm/share/how-to-make-open-source-project-profitable-354.html- Entrevista en IndieHackers: https://www.indiehackers.com/interview/making-15k-month-by-switching-my-freemium-product-to-paid-2771241389- Codepen: https://codepen.io/- Codesandbox: https://codesandbox.io/- Upwork: https://www.upwork.com/- Freelancer.com: https://www.freelancer.com/- Flickity: https://flickity.metafizzy.co- Isotope: https://isotope.metafizzy.co- filepond: https://github.com/pqina/filepond- Handsontable: https://handsontable.com- Highcharts: https://www.highcharts.com 

Ritesh Arora talks about how he learned from failures to bootstrap, and then turn BrowserStack into a $60m rocket ship. Produced by Anand Murali Music Credit: www.accelerated-ideas.com/

We continue with the #InsightsPodcast series, and on this edition, we have Ritesh Arora, Co-Founder and CEO of Browser Stack, a mobile and web testing platform. In this podcast you will hear about Ritesh's journey as a young engineer how he pivoted through a few startup ideas before landing on the BrowserStack idea. And how he bootstrapped the startup to more than $20M in revenue - a humongous achievement for any founder. Ritesh comes from a family background in business, and always had an eye for venturing on the entrepreneurial journey. Teaming up with his roommate from IIT Bombay, Ritesh started his first startup in final year of college: building a product for sentiment analysis in 2005, which involved him picking up machine learning and natural language processing way before AI/ML became fashionable. “I read probably about every research paper published on the topic at that time, about 76 of them. Went through them multiple times and came up with our own algorithm.” Unable to come up with a go-to-market for the product, Ritesh and Nakul decided to take up jobs, but the desire to build something consumer-facing got them started soon on their second venture, in the space of information aggregation on the internet. This time around they were even able to gain traction, but monetization and identifying the right business model proved to be a challenge. Ritesh and Nakul spent a year brainstorming before stumbling on the problem that BrowserStack solves today, while consulting with companies that were seeking their help in building machine learning solutions. ‘Testing website on internet browsers' was a challenge for thousands of developers globally and something that Ritesh and Nakul experienced first hand as developers . Ritesh and Nakul, set out to simplify the journey of developers by helping them test and debug their website on different browsers (mainly Internet Explorer at that time). The traction they got this time around was explosive, starting with 10K beta users in three weeks (thanks to John Resig's tweet), moving to a paid offering soon that grew to $20K monthly revenues in about 4-5 months and $1M annual recurring revenue at the end of year one- all this when they were just a team of two, working out of a coffee shop in Mumbai! The focus on global market from day one helped them scale to $20M annual recurring revenue in a span of four years with just a 50 member team. They realised the need to scale up the organization to be able to sustain the growth and decided to get advisors on board who can help mentor the team in the right direction. The fund-raise for BrowserStack was more about finding the right partner than about raising money. Ritesh speaks about the value that a good investor brings on board especially in the scaling phase, because the founder is always doing it for the first time while the VCs have helped many such companies scale. Apart from talking about the journey of choosing the right investor, Ritesh shares learnings for younger entrepreneurs, from the early days and emphasizes on focussing towards solving large problems, getting feedback from customers, not solving for monetizing in early days and building a great product that makes the customer's journey frictionless. “When your customers use your product, they should feel that it has changed their life” he says. Tune in to the podcast to hear Ritesh's phenomenal journey which has become an epitome of bootstrapping your way to success.

Today we have Neal St. Clair on the show who's the founder of East of Western. We dive deep into software, running an agency, and he asks the hosts some questions as well.

Nick Raushenbush is the cofounder of Shogun, and today he teaches us about the power of building a mobile first website.   Shogun is a powerful page builder that seamlessly integrates into platforms like Shopify and BigCommerce. This allows anyone to easily build out their store with a drag and drop editor, no code required.   Nick is also generous is enough to share a a special discount for podcast listeners using Shopify: 20% off any Shogun plan for life! To get the discount, just use this link: https://getshogun.com/d/electric-eye-podcast-20.   To learn more, visit: https://electriceye.io/podcast   Resources: Learn more at http://www.nickraushenbush.com/ Get 20% off any Shogun plan for life: https://getshogun.com/d/electric-eye-podcast-20 BrowserStack mobile & desktop site testing: browserstack.com Heatmaps & visitor recordings: fullstory.com | hotjar.com User testing: usertesting.com | lookback.io Assess website performance: thinkwithgoogle.com | pingdom.com Image optimization and compression: compressor.io Honest eCommerce is produced by Podcast Masters

Accessibility With Luisa Morales TableXI is offering training for developers and product teams! For more info, email workshops@tablexi.com or see our offerings at http://tablexi.com/workshops. The Table XI inclusive meeting Kickstarter is ongoing as this episode is released, see http://tablexi.com/kickstarter for more information. Guest Luisa M. Morales (https://twitter.com/luisamariethm), luisam.com (http://luisam.com/). Summary As many as 15 to 25 percent of your site’s potential users may have trouble accessing it due to some kind of disability. How can you design your site to allow your content to be usable by the widest variety of users? My guest today is Luisa Morales, an engineering fellow at the New York City Mayor’s office for Economic Opportunity. We talk about what accessibility means, how to design your site to be accessible, and what guidelines to use to help ensure success. We’ll also talk about a very literal form of accessibility — making your site behave in a way that it is accessible to users with limited bandwidth or older devices. We’d like to hear from you. What issues or successes have you had with accessibility? Let us know at techdoneright.io or on Twitter at @tech_done_right. Notes 02:15 - Defining “Accessibility” and the Population Who May Be Affected - W3C Guidelines (https://www.w3.org/standards/) 05:00 - What Web Devs Can Do To Makes Sites Accessible 07:30 - ARIA (https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA) 09:55 - How Screen Readers Work 12:45 - How To Build in Accessibility - h1 Elements (https://www.sitepoint.com/h1-html-element/) 17:36 - Approaching Page Design 20:23 - Auditing Accessibility Issues - JAWS (https://www.freedomscientific.com/Products/Blindness/JAWS) - NVDA (https://www.nvaccess.org/download/) - High Contrast (https://support.microsoft.com/en-us/help/13862/windows-use-high-contrast-mode) - ChromeVox (http://www.chromevox.com) - Browserstack (https://www.browserstack.com) - Pa11y (http://pa11y.org) 22:20 - Accessibility Based on Access - Progressive Web App (https://developers.google.com/web/progressive-web-apps/) - Accelerated Mobile Pages (https://www.ampproject.org/) - The minimalist version of CNN is actually at http://lite.cnn.io 26:49 - Accessibility, JavaScript, Single-page Apps and Site Simulation 32:04 - Accessibility is for everyone: Reasons You Should Care Special Guest: Luisa Morales.

As software continues to eat the world, it’s important to recognize the impact of poor quality software devouring your business. Apple’s bold step of identifying 2018 as the year of software quality is a call for other organizations to do the same. How is yours meeting this software quality challenge? In this episode, we’ll Test Talk with Shailesh Rao, current COO of BrowserStack. Shailesh has previously worked with Google to help develop and scale their Cloud Platform, and also led groups at SAP and Salesforce. Get ready to discover the State of Software Quality in 2018 and why it's more important than ever before.

This Frontsider panel episode explores what virtues go into making quality software, such as having tests, making sure software is performant and accessible, and why you should try to avoid technical debt. Transcript: CHARLES: Hello everybody and welcome to The Frontside Podcast Episode 98. My name is Charles Lowell, developer here at The Frontside and your podcast host-in-training. With me today, we're going to have a round table, a Frontside round table. With me today is Elrick. ELRICK: Hey. CHARLES: Joe. JOE: How you doing? CHARLES: And of course, Will. WIL: Hello, hello. CHARLES: Welcome, y'all. We're going to be talking today about some of the things that we do around here, aside from trimming the shrubs and making coffee and snacking on Altoids. Like, way too many of them. Yeah. I was thinking we could talk a little bit about software qualities of relative things, like this software has these qualities. And I think that that kind of lofty goal of software quality is comprised of having a bunch of little qualities. The quality of having fewer bugs or the quality of having these things. And so, talking about all these things that we do and kind of what we do to make sure that we continue to do them. Or the ways that we can ensure that our software has these things. So yeah, we can just start really anywhere. WIL: Yeah. So, one core thing is obviously tests. CHARLES: That kind of falls under we want to have – really, there's two qualities there that we want, right? Is we want to have… WIL: Maintainable software. CHARLES: We want it to be maintainable. We want it to be resilient to change. And we want it to work properly, right? Yeah, so we put tests in place to make sure that that happens. JOE: Tests also inform design in a really positive way. A lot of the time, anyway. WIL: Another thing that we like to include in our apps is responsiveness. CHARLES: Yeah. And just making sure that you have – that it works on a multiplicity of devices, right? WIL: Yeah. And not just the devices, but browsers as well. CHARLES: Yeah. And it turns out it's actually really hard to do that after the fact. WIL: Right. JOE: Yeah. CHARLES: Making sure that lots of browsers, lots of devices. Because yeah, sometimes you have some weird screen width that is on some weird device, and making sure that that works. I guess there's some overlap with testing there, too, isn't it, right? Like you want to be running your tests on those devices at those resolutions to make sure that they're going to work. This is something that we aspire to but I don't think we're quite there yet. It was making sure that our applications are accessible. WIL: Yeah. JOE: I'm very excited to learn more about this as we get into this, yeah. CHARLES: Right, right. And asking the question, how is it that we actually can ensure our applications are accessible? We have very paved roads for making sure that our applications are resilient to change and that they have low bug rates and that they're well-designed via testing. But what is the analog of testing for accessibility? What's the way that you can put those guardrails in for accessibility? I have no idea. And that's an ongoing conversation here at Frontside. JOE: So, I guess I'm curious as to what technologies are actually involved in accessing a web application in – would it be reasonable to say a non-traditional way? I know there's such things as screen readers, but is that all we're talking about? Or what is the ecosystem that we have to consider supporting? CHARLES: I'm certainly not an expert on this. We'd have to get Rob in here to chew our ears off this. JOE: Yes. CHARLES: But from what I've picked up from him and from our conventions with Marcy Sutton and some other folks that we've had on the podcast, it's a big umbrella. So, it's anyone using an application in a non-traditional way. So, whether that can have to do with limited vision, hearing, movement, range of movement, cognitive ability, it's a gigantic whale of a domain. WIL: Yeah. The topic of accessibility can definitely be several podcasts on its own. CHARLES: Yeah. One thing that we've talked about is it would be great if you could drive your test suite through a screen reader or something like that. What would that even look like? There are a couple of open source ones out there, but they're Windows-only. I think it was NVDA was the big one. And then you have a screen reader that then drives the applications in your operating system, so it's going to vary per operating system. So, making sure that it's accessible on Windows, at least as I understand it, is very different from making sure that it's accessible on a Mac. JOE: Yeah, it's like a whole other layer. And it's like BrowserStack outside of the browser. CHARLES: Right. WIL: There are things that you can do from the beginning that will make it easier when you get to that point. It's just like using semantic HTML, knowing when and how to use proper aria labels. All these things, if you do it from the beginning, it's not as big of a task as bolting it on afterwards. CHARLES: Right. And I think we do have a leg up when it comes to web applications. It's within our power to change. There are cross-platform of those technologies. But as you said, it's important to put them in from the beginning. Because as we've seen, for each one of those categories, you're accumulating debt if you don't address it. So, there's technical debt. But I think that technical debt can [inaudible] into a bunch of different areas. So, there's technical debt in terms of the internal quality of your architecture, the way your software components talk to each other. And I think that that's what people mostly think of when they talk about technical debt. But I think in terms of responsiveness debt, there's a slice of the technical debt pie that has to do with making your application responsive. And so, if you don't address making your application responsive, you're accumulating debt and you might not know it. And if you're not making your application accessible, then from the beginning you're accumulating debt. So that if you have to go and try and figure out your accessibility story six months, a year, two years, you might actually uncover and say, “Whoops. I've been swiping the accessibility credit card. And holy crap, with all this. All my fines and penalties and compounded interest. Now I'm accessibility bankrupt.” And that can be scary, right? WIL: Yeah. And a lot of people don't realize with all this debt after the fact is they think they're going in and adding things like responsiveness and accessibility and tests. But really, you're also taking away previous work that's already there, things that need to be refactored. If you put these things off, you're not just adding a few hours of time. You're inflating your time exponentially. CHARLES: Right. Right, exactly. It can be intimidating but I think it's also empowering, because technical debt is like a scary subject. But if you're like, “Oh, we can actually slice our technical debt into a bunch of different categories and address them individually,” just knowing that this is an area where debt can accumulate, that's half the battle. Because the worst thing is debt you don't even see. ELRICK: Yeah. WIL: I mean, [inaudible] is big. That's a big part of accessibility, that, is most people don't think of accessibility. So, that is a huge debt that a lot of companies don't see. JOE: What about something like internationalization where I feel like I've never been in an application where that wasn't punted on to some degree. That's kind of a well-known problem, but it still takes a back burner. Do you think that if accessibility had more exposure as a concern, would it actually get the attention it deserves or is it kind of destined to, “Oh, we'll get to those yaml files later. We'll send those off for translation later,” that type of thing. ELRICK: I don't know. Sometimes I feel as though people feel as though they're trading speed away when they're building applications when they go to implement these things. Like, “Okay, well we're not really going to touch on these right now because that's going to slow us down from pushing out features.” Which is not really true. Because if you don't settle on these things early, you're not really building a solid foundation for your application in the long haul. So, I think people are like, “Oh, we'll just do it later.” CHARLES: Right. ELRICK: And, “We'll just ship features now.” CHARLES: Right. I think that's exactly right. It has this kind of secondary effect where not only do you develop the debt but you develop a culture of accumulating debt, right? Like when it comes to people getting a hold of their finances, the first thing that they have to change is they have to change their spending habits. And that can be the hardest thing. It's not just balancing the equation. It's like saying, “I need to readjust my thinking about this.” ELRICK: Yup. CHARLES: So that I'm not consistently put in this situation again. JOE: So, there's an operative word there, right, in personal finance in that usually if a company is addressing technical debt especially down the road, something that they've punted on for a while, it's far from personal. There's a board of directors or there's a special interest group involved. There's people who want features that are putting money into it. There's a lot of pressure as the company grows and more people are involved. Priorities are more likely to be lost, I guess. CHARLES: Are you saying it can be hard when your culture is spread over that many people, it can be hard to shift? JOE: Absolutely, yeah. And I guess to keep with the dash-first thing, ideally were we starting a company, we would want to start a culture for this company. A culture that recognizes the vulnerability that we all have to technical debt as applications grow. We want that upfront. But the reality is, you know, startups are eager to get things out. Companies that have been around for a long time have high-paying clients that they depend on that want certain things. And yeah, I guess I'm just saying that it has to come in from the beginning. CHARLES: Yeah. And I think that – I don't want to completely disparage technical debt entirely, because technical debt like actual debt, like financial debt, is a powerful tool that you can wield. But it's also, it's like a table saw. You can also easily slice your finger off. It doesn't mean that it's not a useful tool, right? If anyone's bought a house, it's really great that you can borrow money to buy a house. It's great that businesses can borrow money and get small business loans to get bootstrapped. And that benefits us all to have that community. I don't think that – yeah, startups definitely, they need to have technical debt as a tool that's available to them. But they just need to understand the consequences of it and be able to get a hold on it. JOE: That's a super interesting take. I never considered it that way before. CHARLES: Yeah. It's definitely not my take. I actually think the person who coined the term ‘technical debt', that was the original idea. But then people realized that technical debt can also get way out of hand. WIL: It's just like real debt. If you're not paying down a certain amount every so often, it's going to keep growing. CHARLES: Yup. You're going to have to declare bankruptcy at some point and throw out the piece of software if you don't pay a down. And that's going to be more expensive. ELRICK: Yup. That's definitely true. So, I have a question. And we see this all the time repeating itself at various companies, whether it's a startup, a large company, where they put off testing and mobile-first, user-first, accessibility-first. Like all the firsts, they just toss it to the side. Why do you all think that that happens so frequently? CHARLES: I think it comes into people not understanding that if you don't address it from the start, it won't happen naturally. There is a prime motivator that has to happen. If you don't imbue something with those qualities when it's tiny, when it's a tiny seed, a tiny crystal, you're going to have to drill through layers and layers and layers of core to put it at the crystal to begin with. I like to think of software as kind of like a tree. And we eat the fruit of the tree, and that's the features that users use. And we can tell that a fruit is delicious merely by placing it in our mouths. And we can tell what fruit is bad. But we can't really look at the fruit itself to say what caused this fruit to be good, what caused this fruit to be bad. We have to look at the tree. And I think that that's what people miss when they're developing software, is that what you really want to do is you want to build a tree that builds good fruit. You can't just take the fruit off the vine and say like, “Hey, I've got this peach but it doesn't have enough sweetness. So, I'm going to take a syringe and I'm going to inject glucose around it and make it less tart.” You say, “I want a sweet fruit,” right? ELRICK: Yeah. JOE: You could probably actually do that. CHARLES: You could. And that might be a strategy. And we see a lot of software that has those qualities of, “Oh, we're going to make this accessible,” or, “We're going to try and make this beautiful.” I happen to think that pigs are adorable animals and look great in lipstick. But that [laughs]… you could put lipstick on a pig but people can tell. And you can say, “Oh, this peach needs to have softer fruit,” and you can whack it with a mallet to actually make the meat more tender. But people are going to be able to tell. So, what you really need to do is you need to care for the peach tree rather than worry so much about the fruit. Because if you have a healthy tree, then you will have healthy fruit, right? ELRICK: Yeah. So, you want to plant good seeds. JOE: Yeah. WIL: Back to you question, Elrick, about what motivates startups and other companies to put off these things. I think the biggest thing is just time and money. They have this misconception where they're saving a little time and saving a little money now just to add it back later. But in reality, it's going to cost them tenfold time and money for adding it later, versus just spending that little bit of time and money and all that to begin with. CHARLES: That's true. JOE: It could also boil down, as far as just personal intimidation. Not so much like a business side of a thing but maybe just, think of all of the things that you listed, Elrick. It was almost a dozen dash-firsts in there. If you're sitting down at a startup that you started with three friends and just approaching these things for the first time, that's a lot to tack on right upfront. It's intimidating. CHARLES: It is intimidating. I think my message to those people is I've felt intimidated by that. I think my message to those people is like, the nice thing about it is if you attack those, if you tack all of those things from the get go, the features will take care of themselves and feel more effortless as you go on. You say like, “Oh, well actually, I don't worry about a high rate of bugs.” I want to say recidivism, but that's not the right word. A high rate of return, not on money but on – or high rate of bouncing your users. You don't want that. And if you bake that in from the beginning, parts of the software development cycle that were stressful before just aren't stressful anymore. So, if we say, “We want to have a system that is easily maintainable, well let's put that in from the very beginning.” We say that a lot. We deploy to production on day one. But what that means is, we say we have this value that we want the system to be easily maintainable. And so, we're going to do it from day one. That means that we actually – it's not something that we worry about so much on down the road. Whereas that used to be very stressful. I don't know. I remember when I started my career, there were these long release cycles where every six months, you'd release software. And the last month was just absolutely terrible as you try to stand this thing up and get it into production and then realize it's not monitored. There's no one checking the health of this thing. So, it's pissing off users at one in the morning. And… WIL: Beepers. CHARLES: What's that? WIL: Beepers. CHARLES: That's actually a great – there's a story there. The one time I got a beeper, I went canoeing in the canals of London and I tipped over my canoe and I dropped both my cellphone and the beeper that they've given me. ELRICK: What? CHARLES: I never got put on pager duty again. [Laughter] JOE: I'm going to use that next time [inaudible] with an on-call position. That's a good move. CHARLES: I remember, I definitely remember how sour my manager's face was when I turned [inaudible] the cellphone that was like, dripping with water. JOE: He was eating bad fruit, probably. CHARLES: Yeah. [Laughs] So, the other thing is we like to build beautiful applications, right? So, you have to – that match the user experience. You have to spend that time on design and beauty upfront. You will not have a beautiful application after the fact. You just need to bake it in. ELRICK: And accessible design. CHARLES: Exactly. ELRICK: Don't forget that one. CHARLES: Don't forget that, right? A responsive design. WIL: Yeah, accessibility-first in design. Yeah, responsive and all that starts in design phase, yeah. CHARLES: Yeah, all that, right? So, you want a great experience. You want an accessible experience. You want a responsive experience. You want a quality experience. You want a performant experience. That's another quality that you say. Like, “We're going to make sure that this is performant.” If you want that – and that's something that we're not always great about, right? We don't actually put in benchmarks for our software from the get go. But maybe we should. But there's perhaps a hidden cost there that we might be actually accumulating performance debt that we don't even know about. JOE: That's true. ELRICK: Interesting. JOE: So, things that pop up that are new. Like, accessibility wasn't probably always a thing in computing. Internationalization probably wasn't always a concern. Beautiful certainly wasn't a concern if you look on Wayback machine. You will see that to be true, right? [Laughter] JOE: So, all code is tech debt, I would argue. Or at least has the potential to be. And yeah, as the ecosystem as a whole evolves, being responsive to that, having plasticity in that respect, sort of like meta-first. CHARLES: Right. JOE: That could be the real challenge. WIL: Yeah, Charles is mentioning all these experience things. And so, I was thinking X-first is simply experience-first. You want you users to experience a certain quality of your app. That experience needs to start in the conception phase. CHARLES: Yeah. ELRICK: That's true. And even your developers coming in, developer experience. JOE: Yeah. CHARLES: Right. And I think the core of that X-first, that experience-first, is you need to pick which experiences. Because you can't have everything. JOE: Right, yeah. CHARLES: One, there is going to be too much. You have to say, “I'm going to sacrifice on knowing that this is a performance thing. I'm not going to include that in the core DNA of my application.” And there's just going to be things that you don't know about yet that are just unsolvable problems or that don't necessarily work. And you can say, “You know what? Hypothetically, I'm not going to make this an accessible – I'm not going to focus on accessibility.” But then you need to own that. And you need to know that you're accumulating a huge amount of debt around that. And then I think that is a particularly bad trade-off because someone's always going to come along and you're going to have to know that your application is accessible. I think once we clamp down on that, that's going to be something that we have a strategy for and we include at the beginning on every single application, right? ELRICK: Yeah. CHARLES: But I think you need to have, almost like holding the cards in your hand, say, “These are the cards. These are the X's that I'm going to have in my hand. And they are going to be core to my app.” And they're going to be part of the DNA of that tree. So that I know that the fruit is then going to have those qualities. JOE: And then you as an engineer, that goes through an iterative process as well. Just starting out, you have no idea what that DNA should look like. And short of learning from people who are wiser than you who are around you, and reading blog posts and whatnot, really the only way to know the pain of strong-arming internationalization for instance into a 15-year-old Perl application, is to go through it. And then, you know, future trees will not have this DNA. CHARLES: Right. Right. And that's the other thing. Is if you are going to include, if you are going to try and splice something into the DNA, there's a lot of work. And you just need to go for it. You acknowledge that it's going to be a lot of work. And you need to, you just need to own it and go for it. And pay that expense of actually getting it deep, deep, deep into your application's core values. So that then, you don't have to worry about it anymore. Otherwise, you're going to be paying – you're just basically signing up for a lifetime of debt. Right? WIL: Yeah. And then to make the debt analogy even more, it's like people don't understand the total debt. The end debt. People get a $30,000 loan with a 4% interest and they think they're paying back that $30,000 loan. But really, they're paying back $36,400 after all the amortization of their interest. The debt is higher than you can see, always. CHARLES: Right. WIL: And it's true in tech debt, too. React is the new hot thing now, but in 10 years we're going to be on React debt that we're migrating away from. JOE: I hope so. [Laughter] CHARLES: Maybe less, I think less than 10. WIL: Yeah. The debt is always there. And people don't realize how much they have to pay on top of what's visible. JOE: Yeah. It's an invisible vig. CHARLES: What's a vig? JOE: It's interest, in the mafia. CHARLES: Oh. JOE: Sorry. Yeah. CHARLES: I forgot you're Italian. JOE: Yeah. ELRICK: So, for people that are listening, they might be in a situation where they need to advocate to the powers that may be these X-first values. What do you all think that some of the approaches that they should take to say to whomever it is that, “We need to do this first”? Because there's times where you might say, “Hey, we need to do this first,” and people just look and say, “Oh, maybe not.” Then you need to push back on that. CHARLES: In my experience, I find that the tech debt argument is a good one. Because I think it can be, it's both limiting and empowering. Because sometimes it really is the right call to pull out your credit card and put something on it. If you need to buy water and you need to buy food and you don't have any other means, man, put it on the credit card. Right? Seriously. Even if you have no idea how you're going to pay it back. Like, whip that sucker out and stick the chip in. And it doesn't matter how much it costs. And so, sometimes that is the right call. But I think draining it of a moral or a value as a human person thing, and approaching it from a business decision and saying, really trying to attach a cost to it. Because then I think if you can drain out the emotion of it, because people really want something. They're striving to go get it and trying, give them tools to think about it rationally. That I think is a good strategy, to just say, let them know that there is a debt that's being paid here or that's being accumulated here. And it's really large. And maybe even say, “Look, if we were to put this off by six months, this might cost not twice as much. It might cost ten or even a hundred times as much.” So, by saving $5,000 now, you might actually be accumulating $50,000 worth of debt. It's [bigger] than you think. But I do like – so, I think that's one important tool. But I think then also the other important tool is to say, “If we are going to attack this, let's drive it home. Let's put it at the core. Let's make this a value that we hold so that the tree can take care of the fruit itself.” So, if we say that we're going to put in accessibility – because not all projects are greenfields. JOE: Absolutely not. CHARLES: So, what's the message to them? Sorry. You're just SOL. I think if you're a year into a project, two years into a project, and you realize, “Oh no. We need to do internationalization,” recognize that that might be something that's – that's a pillar of your architecture. Or, “We're going to make this application accessible,” don't half-ass it. WIL: Weave it in. CHARLES: Say, “We're going to transform this. We're not going to add accessibility. We're going to transform what we have into an accessible application.” Or, “We're going to transform what we have into a beautiful application.” Otherwise… WIL: Yeah [inaudible]. CHARLES: I would say leave it ugly and focus your efforts elsewhere on things where you do have your values straight. Because you're never going to have everything in line. JOE: No. WIL: Treat software like immutably. You don't add something to it. When you want to add accessibility, you're creating a whole new accessible app. ELRICK: Ooh. That's deep. CHARLES: Yeah. JOE: So, having seen – I don't know. I think it was very apt, looking at it as a business decision. I've seen it go the other way. Because at least among engineers and people on the technical side of it, this can become a very strong moral issue that people feel very strongly about. CHARLES: Because we have to live with the consequences quite honestly, right? JOE: Exactly. And that's a hard thing to translate to say an executive board that may be three levels abstracted away from you and is making those decisions. I've seen people attack or approach this I guess with that emotion built in, with the, “This is the right way to do it. Everybody else is doing it wrong.” It gets nowhere, basically. What needs to happen I think, so you talk about having this beautiful tree. But that also requires beautiful gardeners. And so, where the moral thing or the interpersonal thing comes in is there needs to be kind of an inclusive and encouraging environment that is fostered among the people tending to the tree. And that's a totally separate thing than selling the business value of it. Those things should be completely divorced. CHARLES: Yeah. It's funny. It's always hard to reconcile those two things, right? Because on one you have, “You have to take care of the raw consumption of material and the output of product.” But then also trying to – so, there's some baseline math that has to happen but making sure that that goal, it doesn't slice people. And can enable them to be happy and feel like they're doing good work. And that the things that they're doing is having meaning. It's probably an insoluble problem that we're going to be dancing around for as long as people are around. If there's one thing that we've come to recognize around here, and we've stated it many different ways from a bunch of different angles through the course of this conversation, and I would say through the course of this podcast, but that is if you want to see something in your software, make sure that you attack it from the get go. ELRICK: Intertwine it in your DNA. CHARLES: Exactly. And then you can actually experience the fruit, rather than trying to always, always trying to jam it and change it and get it into the taste you want after the fact. So, I guess that's it. Thank you so much y'all, for this conversation. I really, really enjoyed it. For those of y'all listening, if you want to continue the conversation, you can get in touch with us we are @TheFrontside on Twitter. Or you can drop us an email. We're contact@frontside.io. So, thanks Elrick. Thanks, Joe. Thanks, Will. JOE: Thank you. WIL: Thank you. ELRICK: Yup. It was great. JOE: It was fruitful. [Chuckles] ELRICK: Frontside-first. CHARLES: And well, we'll see y'all around.

Descripcion del programa Diana Aceves, trabaja como desarrolladora front-end, su especialidad es el desarrollo responsive a medida y con ella hablaremos de MobileFirst. ¿Qué implica crear un buen responsive web design? Hablamos de lo que es para aclarar las numerosas dudas surgidas a raíz de una encuesta que realizó en Twitter. ¡Esperamos que os guste el episodio y como siempre nos vemos al final! Recomendaciones Preguntas rápidas: Diana Aceves Quién me ha inspirado: Luis Herrero Quién me ha inspirado: Naiara Abaroa Quién me ha inspirado: Joan León Quién me ha inspirado: Félix Ortega Quién me ha inspirado: Daniel Martínez Quién me ha inspirado: Daniel Fornells Recomiéndanos un recurso: Octuweb Recomiéndanos un recurso: Browserstack Recomiéndanos un recurso: Developer Tools Recomiéndanos a un invitado o invitada: Luis Herrero ¿Qué tema te gustaría que tratásemos?: Progressive Web Apps Contacta con: Diana Aceves Twitter de Diana Aceves Web de Diana Aceves LinkedIn de Diana Aceves Links del programa Ethan Marcotte Using the srcset attribute Recomendaciones de Ignacio Responsive Web Design Mobile First: What Does It Mean? Adaptive breakpoints Mobile First Contacta con el programa Web de WeCodeSign Twitter de WeCodeSign eMail de WeCodeSign Web de Ignacio Villanueva Twitter de Ignacio Villanueva

Kris Van Houten: @krivaten | krivaten.com | Q2 Show Notes: 00:55 - Kris' Interest and Passion for Accessibility 06:07 - Using Ember for Accessibility: Pattern Adoption 10:13 - Context Switch Awareness and Managing Focus 12:08 - Asynchrony and Desired Interaction 14:04 - Building a Form Input Component 19:05 - Things That Are Hard to Catch 22:41 - Assistive Browsers? 28:17 - Making Things Accessible From the Start Resources: Building for Accessibility by Nathan Hammond @ Wicked Good Ember 2015 The A11y Project: Web Accessibility Checklist WCAG 2.0 checklists Why Don't Screen Readers Always Read What's on the Screen? Part 1: Punctuation and Typographic Symbols Mozilla Accessibility Kris' Blog Post Series on Accessibility: Part 1: What is accessibility and why should we care? Part 2: A Primer on Accessibility Part 3: Getting Our Apps Ready for Accessibility Part 4: Building an Accessible Icon Component in Ember Part 5: Building an Accessible Input Component in Ember Part 6: Building an Accessible Alert Component in Ember Part 7: Building an Accessible Numbers Component in Ember Part 8: Building an Accessible Currency Component in Ember Transcript: CHARLES: Hello, everybody and welcome to The Frontside Podcast, Episode 72. My name is Charles Lowell, a developer here at The Frontside and podcast host-in-training. With me today is Wil. WIL: Hello. CHARLES: Hey, Wil. Today, we're going to be talking about accessibility in single page applications with Kris Van Houten who is a developer at Q2. Hey, Kris. Thank you for coming on the show. Today, we're going to talk about something that I know a lot of people's minds here and probably elsewhere on the internet, it's a topic that's getting a lot more attention, which is a good thing and that's accessibility. We're going to explore the niche of accessibility as it applies to single page applications. Now, you're a frontend developer at Q2, what initially got you interested in and passionate about accessibility in general? KRIS: I honestly feel my path to passion in this area has been a little bit unorthodox in a number of ways. I basically started out in total apathy of this topic and over the last year, it has turned into a genuine interest of mine. About three years ago, I remember listening to an episode of ShopTalk Show with Dave Rupert and Chris Coyier and they kind of went on this large rant about accessibility and why more developers need to be concerned and compassion about it. Dave Rupert was talking about his contributions to the accessibility project and I'm sitting back and thinking to myself and this is back then, obviously, "Why would anyone who is blind want to use anything that I'm working on." I basically balked at the idea and disregarded it entirely. At that time, I was just getting my feet wet with Ember working on an application with a company here in Cincinnati and we had these conversations about, "I notice that we put this action or a clickable event on a div element, should we not be doing that? Is it that not something that we should be doing?" I remember sitting back and having this conversation and saying, "The ads been crawled by SEO and Ember isn't yelling at us for doing it. It still works fine so what the heck? Let's just go with it." Basically, every single app that come into since then has basically adopted that same mindset even before I joined the team so I know it's not just me who is thinking this. A lot of developers that have been exercising the same way of doing their code. CHARLES: Right, it's the path of least resistance. Everybody's got a job to do. Everybody's got features to deliver so that practice can be very easily self-perpetuating, right? KRIS: Exactly and I think a lot of developers just don't understand the semantic difference between a div or a label or a button or a link and how browsers can actually treat these difference HTML attributes or HTML tags differently because of how assistive technology can utilize them for per person's benefit. That's where I was a little over a year ago basically. When I first started at Q2, that first week, I got pulled into a discussion about design patterns which is another passion of mine and somehow, that turned into me joining a group that was to establish to figure out how to tackle the task of making our large app accessible. Basically, we had a company come in, audit our application and we got a big fat F for accessibility so it's something that we said, "We need to start tackling this problem." Being that, I just started at the company that week, I was going to tell them no but internally, I was panicking and saying, "I got to figure out what is this whole accessibility thing is and why it's important." I started looking for books, articles on the topic and trying to basically flood myself with information. Two things that really transformed my way of thinking was actually a talk given by Nathan Hammond at that Wicked Good Ember in 2015, where he shows an example of building an application without accessibility in mind so basically, doing what I was doing before which is we're adding actions to div tags, we're not really caring about semantic HTML, we're just making the feature or the application work. But then what he does, which I think is super powerful is he pulled up a colleague of his who is blind and had him try to use the application. He just goes through and you can see the struggle and he's actually vocalizing and talking about where he's [inaudible] with this application. Long story short, Nathan comes back up and makes a few adjustments. DHTML has [inaudible] up again and it's night and day difference just by changing the markup and by dropping in the Ember A11y add-on which helps with focusing the browser in certain areas of the content. He's able to totally transform how's individuals able to use the app. For me, that was a super powerful to come in and see that and see someone actually struggle with a website that they were trying to use. I think, [inaudible] where I always saw accessibility was it will only affects people who can't see and I think that's the other area where I've really started to have that paradigm shift was when I realized that this isn't just people who can't see. It's for people who have motor difficulties, who can't use a mouse and how to use a keyboard instead. People who have various vision issues, whether that's cataracts, colorblindness, glaucoma, dyslexia, some in these effects, not just DHTML but also affects color contrast, the fonts that we're using that impacts every area of application design and development and that's where I started to realize that that was where the paradigm shift happened in my mind where I started thinking to myself we really need to start talking about this more and getting other developers on board in general on this. CHARLES: It can be intimidating, especially when it feels like on a single page application, your divs have to do more, so to speak in the sense that it feels that your HTML is fatter. It's not just a thin layer but your HTML is actually part of the UI. KRIS: Exactly, yeah. CHARLES: When it comes to having this paradigmatic shift that you're describing, when you're looking at your single page applications, are there any insights into the general structure of the application that you feel like you've gained that are foundational, they kind of transcend accessibility? I guess, what I'm saying is, is there any way that you become like a better developer or been able to recognize foundational patterns because of having these insights surrounding accessibility? KRIS: I've been working with Ember for about three or four years now, basically since it was still in beta. Over the last several years, I have started to accumulate a lot of knowledge as to how we can utilize Ember to do a lot of the heavy lifting for us. When I started getting more passionate about the area of accessibility, first question that came into my mind are how can we use Ember to do some of the heavy lifting for us. For example, some of the things that I had done was go through and start working on developing a couple of components that basically cover a lot of things that I find ourselves doing [inaudible] a lot. Whether that might be a component to just plain icon on a page or a component to display input on a page. What we're able to do is using Ember, we can say, "Here's the icon I want to display but if I don't happen to pass in an aria-label attribute, for example. The component will add the 'aria-hidden=true' for me. Being able to really utilize the power of Ember to do some of that stuff for us on the back side of things, I guess you could say it magically. CHARLES: Let me stop you there for a second and unpack that example. What you're saying is, if I'm going to put an input on the page, if I actually don't assign an ARIA role, it's going to hide it from me? KRIS: No. I was thinking of an icon components, say if I'm using Font Awesome, for example and I want this with the trash icon so I wrote a component for our specific icon library that we're using. We pass in the icon that we want to display, again that could be the trash icon and we can also pass in an aria-label attribute to add a label to that span that will be read to the user. But if we don't pass that attribute in, the component will automatically add the 'aria-hidden=true' attribute for us so basically it skips over it. CHARLES: Yes so it won't be just garbage for a screen reader or someone navigating with a keyboard. WIL: Yeah, otherwise the screen reader tries to read the content of the icon CSS which is just the Unicode. CHARLES: Right. KRIS: Yeah. What we really is trying to figure out and what I've spent a lot of my time, especially in writing my blog series on this was while we are using React or Vue or Angular or Ember or whatever, how can we utilize the power of the single page application frameworks to do some of that heavy lifting for us in the background without us needing to explicitly define everything. I'd say, especially when you work on a large team like what I work on currently, we can't expect everybody to be extremely well-versed in the area of accessibility so if we can do some of the work for them and just encourage them to adopt these components in their daily workflow, it does some of the work for us. That's what we're working on and talking a lot about at Q2 is basically this pattern adoption. CHARLES: Right so it sounds like to kind of paraphrase, whether you're working in any framework most of them have this concept of components so really leaning hard on that idea to make components at the very granular level aware of their own accessibility. Is that fair to say? KRIS: Yeah, obviously there's more I'm sure as we go for the conversation about some of the things that I've tackled in this area but long story short, being able to utilize and recognize, you have this extremely powerful JavaScript framework at your disposal to do some of work for you so why not equip to do just that. CHARLES: Yeah. I guess that falls into my next question, which is there are component level concerns and if there are other component level concerns, I definitely want to hear about them but what immediately leaps to mind is there are also cross-cutting concerns of any single page application, what's the state of your URL and if you're using a router. Some of the content on the page is going to be changing and others isn't like how do you cope with that? What are the cross-cutting concerns of an application that span components and then how do you cope with them? KRIS: I think one thing that comes to mind as you're talking is the whole area of context switch awareness. If I click a link, if I go from the home page of an application to my profile page, how does a screen reader know that that content has now changed to present this new information to the user? I know what we were able to do was we were able to drop in the focusing out with component that's put out by the Ember accessibility team, which basically whenever we render to an outlet, that's utilizing this focusing outlet component, it will focus the browser to that main area and start presenting that information back to the users. One area that was at the top of our list as we start tackling accessibility was we need to figure out this whole context switch awareness thing because -- this is back then obviously when we first got started -- back then there was no way for a user to know when the page changed so they would basically be sitting there, waiting for any kind of feedback or whatsoever to be presented back to them and it just wasn't happening. I would say, managing focus is probably one of the top level concerns when it comes to single page applications because it's a single page application so if you click a link, the page isn't completely refreshing, prompting the screen reader to present the information back to user. That's one of the key areas that I think of. CHARLES: What about things like asynchrony because a lot of times, these context switches are not boom-boom, one-two. The content on which you want to focus isn't available yet. Usually, the analog from a visual UI would be a loading spinner or a progress bar. How do you deal with those to say, "Your content is not quite ready. If you're made to wait it's because we want your content to be of the highest quality." KRIS: Sure, yeah. We were able to drop in the focusing outlet components in our application and it took care of a good chunk of the work but it seems like in our application, we're doing something that might not be as conventional as the rest of the Ember community would like them to be so we might not use the model hook as we should. It's hard for the page to know when the contents actually ready, when it's been rendered to the DOM to present back to the user. One thing that I'm currently trying to tackle right now, to figure out how we can remedy that problem. I probably say, honestly that's the challenge I'm working on right now. I don't have a solid answer to that one at the moment. CHARLES: Irrespective of how it plugs into the tool that you're using, what would just be the desired interaction there, regardless of how you make it work? KRIS: I guess, conceptually what I'd be thinking about is how can we notify the user we're loading content right now and whether that we have an alert box that has the ARIA alerts, basically attributes set on it, that we could pass in new, basically notifications to it to let the user know, "Loading content. Please wait," and then once that content resolves, focus them on that main outlet where the content has been displayed to read that content back to the user. That's how we're trying to think about tackling this issue but we haven't have a time to implement it to see how it's going to work across all the different avenues of application. CHARLES: I did want to come back at the component level. are there any other ways that you can lean on Ember or lean on React or lean on Vue, if you're using a component or in framework, just talk a little bit more about how you use those to unlock your application and make it more accessible. KRIS: One thing I can think of is a way that we can enforce better usage of the framework that we're using is one that comes to mind is a component that I worked out in the blog series that I wrote was building a form input component. Especially, when you're trying to write an accessible app, I think about how can we enforce certain patterns when other developers come in later on and want to add a field to a form or use this component somewhere else in the application. What are some ways that we can enforce that they're doing everything, using the component correctly so that way it renders accessible mark up? What I tinkered around with and we actually just landed in our application is basically a form group component to where we pass in, obviously the value that the input is bound to. But we also pass in a label that is tied to the input and whenever you hit save and the app goes to refresh, if you don't pass the label, there's an assert statement that basically fires up an error into the console and lets you know, "You're trying to use this component, you need to pass into label attribute for the purposes of accessibility and here's the instructions on how to do it." We've been kind of toying around with this idea of enforcing patterns because again, we have several dozen developers at Q2 that are working on this stuff and they're not all wizards when it comes to accessibility but how can we gradually start getting them to the place where they're adopting these patterns and best practices. I'd say, doing things like that, we are enforcing patterns in the usage of the components as well is really a key. One thing that we implement it in our testing framework is the use of a Deque Labs' aXe engine to basically go through, we can pass it a chunk of HTML and it will give us any suggestions that it has to make that content more accessible. We're using that in our test library right now, in our test build and encouraging developers as they write new components, as they go in and modify components to throw new snippets in to make sure that the content that's being spit out here is accessible and then submit your PR again. Just trying to be more hands on in that way. CHARLES: So you actually running a GitHub agent or something that's actually in the same vein as your test suite or if you're taking like snapshotting with Percy for doing visual diff so you're actually running a third check, which is an accessibility check? KRIS: Right now, we were able to land the aXe engine into our test build a couple months back so we're just slowly incrementing that over time. We have a couple challenges in the way of getting Percy implemented but that is in our list of goals to have that running as well. But one thing that I really like about aXe engine in particular is that if your check fails, it refines improvements that you should be making. The nice thing about it is also spits out a link to a page on Deque Labs website. They give an explanation of what have found and basically educates your developers for you. To me, I think that's huge because again, we can't educate every single developer and expect them to be pros at this but we can utilize tooling like the aXe engine or the [inaudible] Chrome extensions or stuff like that to do some education for us. As we work towards automating this further and further by using the aXe engine in our development side of things or using Percy on the test build as well. See, there's all kinds of stuff you can do but that's where we are right now. CHARLES: I really like that idea because in comparison with what we talked about at the top of the show, about how there's this path of least resistance that developers will follow quite naturally and quite rationally, which can lead to not accessible applications. It sounds to me like what you're doing is a establishing the same path of least resistance but having that path guide you towards accessible applications and saying, "This path of least resistance thing, it can be an asset or a liability so we might as well make it an asset." KRIS: Yeah, for sure. We sit down once a week and we talk about whatever challenges we're trying to work through in terms of accessibility. We have a weekly meeting where we sit down and talk about it. I thought one of the key topics to those conversations is how do we get the other developers that are not in these meetings more aware, more informed and more up to speed with this that they care about it, that they're working on it and it's part of their inner dialogue as they're writing out new features that are going to be deployed out to our clients. Lots of challenges there. CHARLES: Yeah. We've talked about some of these problems that you catch, you're actually writing some assertions there on the test build so you'll actually fail if there's certain requirements that aren't met but what are the things that are more intangible? How do those come up in terms of accessibility? What are the things that you can't catch through automated testing? KRIS: Right now, some of things that we're having a hard time testing which Percy will help once we get that implemented is contrast ratios and stuff like that. That's one of the key things that comes to mind for me when I think of the things that are a little hard to catch. I think another thing that's hard to catch, especially at the aXe engine and stuff like that, won't necessarily catch is the flow of your dialogue. When I turn on a screen reader and it starts reading back this page and content to me, sure we can make it so that it doesn't read out the icons character code and a lot of stuff. It presents the information we want back to us but I think, having that information presented back to the user in a way that's legible, that makes sense to them is probably one of the bigger challenges that I've been working on a little bit. One that comes to my mind is like the reading of currencies or numbers. One thing that I found way helpful was Deque put out a very thorough article on how the different screen reader like JAWS, NVDA, Apple's VoiceOver, how they read different types of punctuation, different types of graphics symbols, how they read [inaudible], $123.50, what does a screen reader actually read back to you. That's where I've actually been spending so much of time lately is building on some components that instead of reading back what the streaming will read back by default, which should be, "Dollar sign, one-two-three-five-zero," having actually read back, "One hundred twenty-three dollars and fifty cents," so basically, writing a series of components, I would do some of that, again heavy-lifting force, in that way, our developers don't have to go in and manually add-ons aria-labels obviously. That's been a nice little challenge where something that's we are working on just testing right now and making sure it works right if there is any downsides to doing this but I want a person using a screen reader or other types of assistive technology to hear the information as I'm thinking about it. When I see $123.50, I'm thinking in my head that's, "One hundred twenty-three dollars and fifty cents," not in single digits one right after the other. Those are things that a lot of the automated software isn't catching. It's not catching like, "Your grammar is bad," or, "This isn't making any sense to me." It is catching like are you passing in or applying the attributes to HTML elements that you should be. Are you using semantic structure in your headings and stuff like that?" I think that's one of the areas where developer is need to get their hand dirty, turn on the a screen reader or use any array of different voice-over tools to actually listen to the content being present back to them to see how it's presented. CHARLES: Yeah, it's almost a difference between a syntax error versus a runtime error like we've got a lot tools that can catch the syntax errors and you can put those in and catch where you have something that's malformed but some sentences can be perfectly formed but make no sense and it takes a human set of eyes to make sure if that content is coherent. One of the things that if you're going to ship applications to people, you need to be able to try and measure as closely as possible the environments in which the people will be using your software so you can actually have an accurate measure of whether it works or not. For example, in the Ember world lately in the stuff that we've been doing with acceptance testing in React, we admit people are going to be using a multiplicity of browsers to access this application so it's very typical to use Testem or use Karma to fire up five different browsers, which if you're using BrowserStack, you can do fifty. You know, people are going to be using IE8.1 on Edge or on a Surface. They're going to be using Safari. They're going to be using Chrome and those often surface those issues but I feel like there's no access to the actual screen reader and assistive technologies to be able to make real assertions against those things. I imagine that it would be cool if there was some way that in Testem or in Karma, you could have one of your browsers be like an assistive browser that you could actually assert, I want to assert that it read it as, "One hundred fifty-three dollars and twenty-five cents," and is that on the horizon? Is that even possible? But it seems like something that we have to shoot for if we actually want to measure that these things are working if we actually want to capture data points. KRIS: Yeah, I totally agree. If you look at the documentation on W3 for how these different HTML attributes should be treated by the browser or by the assistive technology, long story short is this is not how -- in several cases -- certain screen readers are presenting the information back to you. It's not how it's treating the content. That's again, one of the areas I thought was way interesting about that. Deque article on punctuation and typographic symbols, which is like we should expect that this software is operating at this level to present this information back to user in such a way where it understands what the dollar symbol in front of a series of numbers means but it just isn't there yet. There's still work to be done. I'm hopeful for the day where our screen readers are a lot more powerful in that capacity. One that makes me a lot more hopeful about that is I don't know if it's just because I've been more interested about this over the last year but it does seem like I'm seeing a lot more people talk about accessibility. I'm seeing Apple putting out videos, talking about the efforts that they're making to make their software more accessible. It does give me hope that there's a lot more visibility on this now. There's a lot more people fighting for this cause to cause these companies to come back and say, "We're going to put more effort into this. We not just going to make a standard screen reader and ship it and just leave it there for five years and no one was going to touch it," but, "We're going to start making improvements." One thing that I did notice just over the last couple months even was that out of nowhere, we use Apple VoiceOver in Chrome, which isn't typically how people use it. They typically use it with Safari. But if you use in Chrome, it will actually read back to you as, "One hundred twenty-three dollars and fifty cents." When I came across that, I was kind of dumbfounded but then I was thinking to myself, the vast majority of people who are using screen readers aren't using this browser but that's really interesting that they're doing this now. I dream of that day where we can basically run a series of mark up through in a test or into a function and basically have to spit back, here's how screen readers going to present this back to you. I'm hopeful for that day. CHARLES: I'm wondering now like why don't major browser vendors, why is this not just a piece of a puzzle that comes when I download Firefox. Firefox has access to my speakers, why isn't there a web standard for how screen readers will treat content? Maybe there's an effort under way. KRIS: I sure hope so. Looking through documentation, we know how things are supposed to work, how we've agreed that they should work and now basically, we're just waiting for the different browser vendors and Microsoft and Apple to make the updates to their streaming technology as well as JAWS and NVDA. I'm hopeful that these changes come soon. These are improvements to the interface. CHARLES: Yeah. Any time there's a gap, you can see that's an opportunity for someone -- KRIS: For sure. CHARLES: -- To write some software that has some real impact. I know certainly, I would love to see some way to roll these things into our automated test suites. KRIS: Yeah. I searched for it but with no avail and it's a little bit beyond my knowledge of how to build something of that caliber. I hope someone else does it because I don't know how. [Laughter] CHARLES: Well, maybe in a year, maybe in two years, maybe in 10, although hopefully a lot sooner than that. KRIS: Yeah. I would judge that at the speed of things were going right now, I'm optimistic that we're going to have some much better solutions within the next year or two on this field. Especially of how much I'm seeing people talk about it now, how much it's becoming a part of the regular conversation of web development, application development. I'm really optimistic that we're going to see some strides in this area over the next couple years. CHARLES: Okay. With the time that we have left, I'm going to ask one more question. Kris, there is something that I wanted to ask you, which is let's say that I am a developer who is working on a team that is maybe it's big, maybe it's small. I've got an application or I'm starting an application and I have a desire to make it accessible. How do I establish that path of least resistance? What advice do you have for someone who's just about to take the first step on that journey to make sure that they have the outcome that they're looking for which is the most accessible single page app that they can have? KRIS: I think it's a great question. I would start out that answer by simply saying to encourage you to be somebody who cares enough to speak up and become an evangelist, become an educator and become an enforcer in your workplace for this work. You don't have to be the most knowledgeable person in the world on the topic. God knows I'm not and I still there were people come to me, asking me, "How do I make this feature, make the guidelines, make it accessible to screen readers," but I'm passionate about this topic and I'm interested in learning as much as I can about those. Step one, just being an evangelists for it. Be interested in it, care about it. I'd say, the next thing is just learn more about semantic HTML. I would say from a lot of the things that I've been trying to tackle with the application that I'm working on, just simply writing semantic markup takes care about 80% of my challenges. In just understanding what are the different elements, what are the different tags are for and how screen readers and other assistive technology see those things. To get started, I would say there's beginner, intermediate and advance stuff. I would say go to the accessibility project, which is just A11yProject.com and read through the content there. It's very entry-level. You can probably read through most of the content within an hour or two and really start to get a grasp as to what level of effort you're looking at in terms of your application. Once you get through that, if you still want to learn more, I'd say go over to Mozilla's developer network -- MDN -- and read through their documentation. On the topic, there is a little bit more exhaustive but it's still really easy to read and really easy to grasp. Based on a content they have shared there, I'd say more of an advance level is actually go through all the documentation on the W3. It's a lot more verbose, it covers a lot more of use cases, it has a lot more suggestions and just stuff ready to go over. I'm still working through that information. There's so much of it but I would say that's as a good place to get started with understanding the different attributes, what they're for and just the importance of writing semantic HTML. I would say some definitely good things to start tinkering with to find some of the low-hanging fruit in your application would be to use some of the assessment tools that are already out there. You have the [inaudible] little JavaScript snippet that you can put in your Chrome favorite's bar or you can use the aXe engine or if you even have an aXe Chrome extension that you could pop up in your application to basically give you report on some of the areas that you should be looking to make some improvements. I think it's important to view accessibility kind of like how a lot of bloggers view SEO, is that there's always more work to be done, there's always improvements you can make but the key is to take those first steps and start making those improvements. One of the nice things about the accessibility project and there's a couple other websites out there that have some of the lists, they basically have a checklist for you to go down. If you're just getting started with accessibility, they have a checklist of all the first things that you should be covering to get your app started in that realm, to start making those improvements. I know you guys do links in the show notes. I can definitely send you those things to those items to get people started. Another thing I find myself doing a lot is while we're talking about something in our chat at work in or just go off in the code pin and mock something out in HTML and then see how the screen reader reads our content back to me and then kind of tinker with it and do a little bit of self-discovery in how this all works together. There's a lot of options out there. I know just threw a lot at your listeners but I'd say, it all starts with being someone who cares about the topic and cares enough to start asking others to care as well. CHARLES: I think that's a fantastic answer and a great note to end on. But before we go, obviously we will include those things in the show notes but also the other thing that we're going to include is a link that you actually, I understand, have a series of blog posts related to all of the things that you've been talking about, which we'll also include. KRIS: Awesome. Thanks. CHARLES: Everybody, go read it. Thank you so much Kris for coming and talking with us about accessibility. I think you're right. It is a topic that's gaining a lot more traction and a lot more mind share in the mainstream that can only be a good thing.

Our weekly Saturday round-table focuses on the processes we use to intake clients, design and develop websites, test and launch, and have ongoing relationships. What are the tools they use? And what are the internal processes that the panel have developed to help them manage projects? The panel this week: Lee Jackson http://leejacksondev.com/ Sallie Goetsch https://www.wpfangirl.com/ John Locke https://www.lockedowndesign.com/ Jonathan Denwood https://www.wp-tonic.com/   Episode 148 Table of Contents: 0:00 Podcast Intros 1:13 WordPress News Story #1: Flywheel Acquires WordPress Local Development Tool Pressmatic https://wptavern.com/flywheel-acquires-wordpress-local-development-tool-pressmatic 9:42 WordPress Story #3: PDF Image Previews Among the Improvements to Media in WordPress 4.7 https://wptavern.com/pdf-image-previews-among-the-improvements-to-media-in-wordpress-4-7 19:55 WordCamp 2016 2 to 4th of December 2016 https://2016.us.wordcamp.org/ 23:10 The processes for the various stages of web projects. 23:58 Our processes for getting clients to sign on the line that is dotted. 38:35 What does your client onboarding process look like? 51:49 What does the creative phase of the project look like? What comes first, middle, and last? Content first or design first? 1:10:02 Podcast outros ===================   Links mentioned during the show: Announcement: Leadpages Has Acquired Drip https://www.leadpages.net/blog/drip-acquisition/ WP Media Folder - Media manager with folders https://www.joomunited.com/wordpress-products/wp-media-folder Mike Monteiro: F*ck You, Pay Me https://www.youtube.com/watch?v=jVkLVRt6c1U WPBuilds Episode 3: Clients from heaven (not) https://wpbuilds.com/2016/12/02/episode-3-clients-from-heaven-not/ WP Innovator: Our WordPress Website Build Process http://leejacksondev.com/wpinnovator/51-our-wordpress-website-build-process/ How to Write a Book: The Secret to a Super Fast First Draft http://www.smartpassiveincome.com/tv/how-to-write-a-book-fast-first-draft/ Seanwes Episode 13: You Design the Content http://seanwes.com/podcast/013-you-design-the-content/ Freedcamp https://freedcamp.com Pocketcasts https://www.shiftyjelly.com/pocketcasts/ Browserstack https://www.browserstack.com/ Heering - The Original Cherry Liqueur http://www.heering.com/ ===================   Find bonus content for this episode on the WP-Tonic website: h

Whether build the site from scratch or with a template, it is essential you check your WordPress website works on multiple devices. So with so many out there, what should you be testing and how!? Let us share how we do it... Blisk - https://blisk.io/ BrowserStack - https://www.browserstack.com --- OUR EVENT: Do you want to make real change in your business? Join us at our in-person event Agency Transformation Live Meet Troy Dean; Lee Jackson, Chris Ducker, Kelly Baader, Amy Woods, Paul Lacey, Dave Foy and other legends in this fantastic conference focused on actionable steps that you can use to transform your agency. --- See acast.com/privacy for privacy and opt-out information.

In this episode Reda and Kyle talk about browser testing. They discuss how they approach testing each browser and operating system and devices. They talk about the differences in type rendering, browser user interface, and layout. Reda talks about how he approaches a simple fluid layout, Kyle talks about his most recent project and some layout challenges and they talk about using CSS for layout. Browserstack IE blog post IE Setup Feedback episode

This week, Mark declares that he's ready to Go Live! We chat about finding work, last-minute concerns, and other nonsense. My Toolstar this week is BrowserStack, a service that allows users to fire up other Browser/OS combinations from within their browser: http://www.browserstack.com My Jukebox addition is 'In Praise of Shadows' by CFCF. Mark's is 'Aquarius' by jukebox perennials Boards of Canada. Both tracks are added to the Relative Paths Spotify Playlist (http://relativepaths.uk/pl), and while it exists, the Apple Music playlist too (http://relativepaths.uk/am). The music we use for various intro bits, stings and outro is ‘Vitreous Detachment’ by Origamibiro, used with kind permission. If you listen regularly, please leave a review or comment wherever it is you like to listen to us. Sometimes we like to know people are listening, and what we can do to improve. We’d particularly love an iTunes review: http://relativepaths.uk/it – Ben Subscribe and keep in touch: iTunes - http://relativepaths.uk/it Stitcher - http://relativepaths.uk/st SoundCloud - http://relativepaths.uk/sc Twitter - http://twitter.com/relativepaths Facebook - http://facebook.com/relativepaths

本期由 Terry 和 袁滚滚 一起主持， 邀请到了 Vue.js 的作者 尤小右, 聊聊前端框架开发背后的故事。 这一期我们将聊到非常多前端框架和技术，大家也可以听到小右同学对各种前端框架和技术的点评，如果你正愁如何选择你的前端工具栈, 我相信这一期将会对你有非常大的帮助。(涉及到的技术包含 Knockout, BackboneJS, Spine, Marionette, AngularJS, Ember, Ractive.js, React, Flux, webpack, Karma， Jasmine 等等等等) Meteor Parsons School of Design Clojure Colgate University ActionScript Zachary Lieberman openframeworks three.js Google Creative Lab Google Data Arts Team Aaron Koblin Chrome Experiments Dependency injection Object.defineProperty() Knockout Backbone.js Spine AngularJS Marionette MVVM Glimmer Ractive React React Virtual DOM shouldComponentUpdate (React) Flux Immutable JS CommonJS substack Browserify webpack Babel CoffeeScript TypeScript Jasmine Mocha Karma Selenium CasperJS PhantomJS Nightwatch.js Sauce Labs BrowserStack DailyJS Laravel Laracasts Processing TasteJS Avalon 尤小右 知乎 Relay Ember FastBoot react-server-example 功夫熊 硬派健身 硬派健身 － 知乎专栏 Python China 青城 Theme BTW: 录制中途，突然楼上开始敲东西，虽然后期做了一些处理， 但是可能还是略有影响，但并无大碍，希望大家多多饱含. 小右口误更正： 小右到达美国的时间是 05 年 Typescript 是有类型推导的 Special Guests: 尤小右 and 袁滚滚.

In this month’s podcast, Megan Taylor from Kapow Interactive walks us through a typical web project from start to finish. Tune in for Episode 45 of the Business Catalyst podcast! Listen to this month’s podcast: Simply click the play button below to stream the podcast via your browser. player AudioPlayer.embed("player-nov1320", {soundFile: "http://www.businesscatalyst.com/LiteratureRetrieve.aspx?ID=126653", noinfo: "yes" }); Alternatively, you can download the podcast in .mp3 format for offline listening. In this episode: Michael Sallander’s big announcement Megan walks through Kapow Interactive’s process Megan shares what she wishes she knew when starting out Important Takeaways: Don’t forget about offline marketing. It makes sense that a web professional would market themselves online. And, in many cases this is a good strategy, but don’t forget about marketing yourself offline. Megan works closely with her local Chamber of Commerce, wraps her car with her company information, and even advertises in the local newspaper. Every area is different so experiment with your marketing, but don’t forget about traditional marketing. Say no to work, but keep in touch. It’s smart not to spend too much time with clients who aren’t ready to invest in their online business. This is why Megan says “no” to some work. However, she keeps track of these potential clients. When work is slow, these contacts can be valuable leads. Many of these contacts could now be in a better position to pay for online services. Work on your business. If you start a website-building business, you probably already know something about building websites. Put some time into learning the business. Educating yourself in sales, marketing, and accounting will help you build a successful business. To learn more, listen to Megan’s entire interview. Scott B Reynolds - Thrise Resources mentioned in podcast: Kapow Interactive - http://www.kapowinteractive.com.au/ BrowserStack - http://www.browserstack.com/ BC App Store - http://www.bcappstore.com/

This week, Dave and Gunnar talk about: computers that think, computers that think they’re thinking, and people that think computers are people. Gunnar is a Trello addict The Mother of all Web Tracking Catalogs. I think we’re done now. Housewarming gift via Heat template: Germans get free heating from the cloud BrowserStack gets utterly humiliated ChatOps is just thrilling User modeling with Watson That Time 2 Bots Were Talking, and Bank of America Butted In The ultimate weapon against GamerGate time-wasters: a 1960s chat bot that wastes their time Lauren and her juggling app mentioned on Gizmodo and Lifehacker UK GCN wins Gunnarbait of the week Preceded by this article on DHS and Coverity. Succeeded by Dave’s article 6 tips for adopting open source published on GCN RHEL Atomic beta now out! Dave keeps the SELinux on in the Docker docs OpenShift Enterprise 2.2 is out, with Fuse and A-MQ Messaging cartridges (xPaaS!) and CloudForms integration https://install.openshift.com/ is mind-blowing. Red Hat Enterprise Linux 6.5 to 6.6 risk report Google Cloud Platform says: “Red Hat has contributed tirelessly to almost every component of the stack and has been instrumental in shaping and improving the overall production readiness of Kubernetes.” Not my circus, not my monkey: Idioms of the World HT Bob St. Clair and related: Management Time: Who’s Got the Monkey?  Cutting Room Floor Cat Math What Happens When A Photographer Secretly Takes Over A Town’s Surveillance Camera Software-Defined Talk Podcast We Give Thanks Bob St. Clair for monkey management tips

Note: The hashtag for the show on Twitter has changed, please connect with us using #DtSR going forward. Thanks!   Topics covered Update: Home Depot breach (Hint: apparently it was a 3rd party entry point) Story: http://www.computerworld.com/article/2844491/home-depot-attackers-broke-in-using-a-vendors-stolen-credentials.html Apparently as a reaction, all execs are being switched to iDevices (blame Windows? and why only execs?) - http://www.imore.com/home-depot-switches-execs-iphones-macbooks-it-blames-windows-massive-breach Also, they lost ~53 Million email addresses too - http://online.wsj.com/articles/home-depot-hackers-used-password-stolen-from-vendor-1415309282 American Express is pushing tokenization to their payment ecosystem, this is big news but leaves a lot more questions and concerns than answers (for example- what about chip & pin (sign)? )- Story: http://threatpost.com/american-express-brings-tokenization-to-payment-cards/109137 Check out the standard itself: http://www.emvco.com/download_agreement.aspx?id=945 Flaw found (in a lab) in the VISA EMV protocol, but is it realistic to do this kind of "immense fraud" in outside the lab, in real life? Story: http://www.cio.com/article/2842994/flaw-in-visa-cards-could-ring-up-a-very-large-fraud.html The FTC further exerises its (Constitutional?) powers to take down fake "Support call scammers" and is on track to some public fanfare- Story: https://nakedsecurity.sophos.com/2014/10/26/ftc-takes-down-fake-support-scammers-upbeat-about-getting-consumers-money-back-poll/ Connecticut Supreme Court paves the way for class-action suit in HIPAA breach/violation. Big question- is this good for anyone other than the lawyers? Will it just add to the rising cost of healthcare, or is this doing some good? Story: http://www.ctlawtribune.com/home/id=1202676138225/Conn-Supreme-Court-HIPAA-Decision-Likely-to-Spawn-More-Litigation A "spying software" that can spot a phone theft in "2 minutes"? Call us skeptical, and leary- Story: http://www.fastcodesign.com/3038031/spying-software-spots-phone-theft-in-2-minutes-no-password-needed Starwood Hotels is going keyless with iPhone & iWatch integration for room entry. A great idea, if it's free of the usual security bugs. Story: http://www.theipadfan.com/starwood-hotel-rooms-now-keyless-with-iphone-and-apple-watch-app-integration/ Michael's take on the story: http://www.csoonline.com/article/2691383/security-leadership/what-did-you-expect-to-happen-when-you-bought-the-electronic-lock.html Episode 111, where we briefly cover this topic in detail via the Onity court case: http://podcast.wh1t3rabbit.net/dtr-episode-111-newscast-for-september-22nd-2014 Breaches BrowserStack goes down, gets transparent and honest, promises to come back stronger - http://www.browserstack.com/attack-and-downtime-on-9-November "Massive" USPS data breach identified, hits customers and employees (cue the lawsuits!) - http://www.cnn.com/2014/11/10/politics/postal-service-security-breach/index.html?hpt=hp_t2 NOAA breached by .... China! - http://www.eweek.com/security/noaa-other-u.s.-agency-security-breaches-connecting-the-dots.html State Department shuts down unclassified email system, after spotting "activity of concern" - http://www.nytimes.com/2014/11/17/us/politics/state-department-targeted-by-hackers-in-4th-agency-computer-breach.html?_r=0

There are many tools for showing you screenshots of websites in different browsers to help with testing. But a screenshot is lacking in so many ways: no clicking, no hovering, no typing, no resizing, no testing JavaScript or other interactive elements, nothing. Real cross-browser testing means opening those websites in real live browsers. Some people use virtual machines to do that testing, but that can be resource intensive in more ways than one. BrowserStack is the holy grail of cross-browser … Read article “#106: Use BrowserStack for Live Web-Based Cross Browser Testing”