Do you have an idea for a product or service, but need the expertise of seasoned web developers and architects to build it from start to finish? Let our team handle the heavy lifting for you. We will help you from ideation, through iteration, and on to creation using the latest technologies, tools and industry best-practices.
Let's talk
Application StrategyWork hand in hand with our architects to assess requirements and goals for development. We can help you think through strategies for optimal go-to-market as well as how to best create cross-functional, multi-platform applications.
We can help your ideas come to life and ensure long term sustainability of the project as features get added.
Rapid Prototyping and DesignOur process begins with an in-depth design process where we rapidly iterate with you on the designs and user experience for the project before ever writing a line of code.
This process leads to a decreased time-to-market and optimizes costs involved to build the project. Our focus is helping you deliver a high-quality user experience while optimizing for quality and performance of the application.
DevelopmentWe provide a fully integrated team dedicated to your project. Our team will ensure best quality development, test suites, documentation, and ongoing maintenance and feature development of applications.
While many of our clients prefer to stay with us for long term support of their applications, we are also invested in the future of your project and your future goals. We often train internal teams on new applications and facilitate an application hand off so companies can maintain their projects internally long term.
Project ManagementOur team will own the project management process and keep you informed on a daily and/or weekly basis. Before we begin, we’ll establish timelines with you and continue to monitor and assess risks throughout the process. We work with stakeholders to keep them informed of deadlines and deliverables.
Part of our project management process is ensuring that your application is delivered with full documentation on features, fixes, configurations, and more.
Building for the FutureOur team consists of expert engineers that have experience in open source and are core contributors to major frameworks and libraries in JavaScript. With our background and expertise, we generate forward-thinking solutions that will help your organization stay up-to-date with the latest technologies.
MentorshipWe value learning, teaching, and mentorship. This helps ensure the solutions we architect and build are built to last. With our mentorship focus, we are also invested in helping your team learn and grow during our engagement with you.
Our clients are building for the future. Explore This Dot Labs' portfolio, and see how we have helped them achieve their diverse technical goals.
We're ready to be your trusted technical partners in your digital innovation journey.
Whether it's modernization or custom software solutions, our team of experts can guide you through best practices and how to build scalable, performant software that lasts.
Our clients are building for the future. Explore This Dot Labs' portfolio, and see how we have helped them achieve their diverse technical goals.
topics covered in this case study:
This partnership set a new standard for leveraging pharmaceutical research outreach technology, showcasing our commitment to innovative, high-performance solutions.
topics covered in this case study:
Ahead of Google I/O in May 2023, the Angular Core Team reached out to This Dot Labs to help them deliver a demo application, showcasing a highly interactive ML integrated application built using Angular with TensorFlow.js in time for the conference.
topics covered in this case study:
Supported by a Chainlink Community Grant, This Dot Labs recently created Smart Contract Database (DB), an open-source website for the Chainlink developer ecosystem.
topics covered in this case study:
The Wikimedia Foundation is the non-profit media organization behind Wikipedia. Part of Wikipedia’s push for wider use includes Abstract Wikipedia, which provides a language-agnostic version of Wikipedia articles by utilizing natural language generation to provide content in supported languages.
I recently participated in an audio space with the Stripe team, and something they said really stuck with me: the Stripe app store is a growing area that isn't overly saturated yet....
Dec 18, 2024
4 mins
Svelte 5 was finally released after a long time in development. Fortunately, we've been able to test it for some time, and now it has a stable release....
Nov 27, 2024
4 mins
As web developers, we're often working with external data that we don’t control and can’t expect to meet our expectations. But with the Zod library, we can define expected data schemas and validate incoming data against them....
Nov 15, 2024
7 mins
Understanding the Difference Between :focus and :focus-visible in CSS I have learned my fair share about the importance of keyboard accessibility, so I know that visual indication of the focused element is very important. But the well-known :focus pseudo-class is not always the best fit for this job. That's where :focus-visible comes in. Let's look at the differences between these two pseudo-classes and explore the best practices for using them effectively. What is the :focus Pseudo-Class? The :focus pseudo-class is a CSS selector that applies styles to any element that receives focus, regardless of how that focus was triggered. This includes focus events from keyboard navigation, mouse clicks, and touch interactions. Example Usage of :focus ` In this example, the button will display a blue outline whenever it is focused, whether the user clicks on it with a mouse, taps it on a touchscreen, or navigates to it using the keyboard. What is the :focus-visible Pseudo-Class? The :focus-visible pseudo-class is more specialized. It only applies styles to an element when the browser determines that the focus should be visible. This typically occurs when the user navigates via the keyboard or assistive technologies rather than through mouse or touch input. Example Usage of :focus-visible ` Here, the button will only show a blue outline when focused through keyboard navigation or another input method that usually requires visible focus indicators. Key Differences Between :focus and :focus-visible :focus - Behavior: Applies to any element that receives focus, regardless of the input method. - Use Cases: Ensures that all interactions with the element are visually indicated, whether by mouse, keyboard, or touch. :focus-visible - Behavior: Applies styles only when the focus should be visible, such as using a keyboard or assistive technology. - Use Cases: Ideal for scenarios where you want to provide focus indicators only to keyboard and assistive technology users while avoiding unnecessary outlines for mouse and touch users, typically required by design. Accessibility Implications :focus - Pros: - Guarantees that all users can see when an element is focused, which is critical for accessibility. - Cons: - Can lead to a suboptimal experience for mouse users, as focus styles may appear unnecessarily during mouse interactions. :focus-visible - Pros: - Enhances user experience by showing focus indicators only when necessary, thus keeping the interface clean for mouse and touch users. - Tailors the experience for keyboard and assistive technology users, providing them with clear visual cues. - Cons: - Additional considerations may be required to ensure that focus indicators are not accidentally omitted, especially in older browsers that do not support :focus-visible. - There may be cases where you want to show focus indicators for all users, regardless of input method. Best Practices for Using :focus and :focus-visible To achieve the best accessibility and user experience, combining both :focus and :focus-visible in your CSS is often a good idea. Combining :focus and :focus-visible ` Here is a Stackblitz example of what such styling could look like for you to try out and play with. Additional Tips - Test with Keyboard and Assistive Technology: Ensure that your web application is navigable using a keyboard (Tab, Shift + Tab, etc.) and that focus indicators are visible for those who rely on them. It's never a bad idea to include accessibility testing in your e2e testing suite. - Provide Clear Focus Indicators: Make sure that focus indicators are prominent and easy to see. A subtle or hard-to-spot focus indicator can severely impact accessibility for users who rely on keyboard navigation. Conclusion The :focus-visible pseudo-class offers a more refined way to manage focus indicators, improving accessibility and user experience, particularly for keyboard and assistive technology users. By understanding the differences between :focus and :focus-visible, and applying best practices in your CSS, you can create more accessible and user-friendly web applications. Remember, accessibility should never be an afterthought. By thoughtfully applying focus styles, you ensure that all users, regardless of how they interact with your site, can easily navigate and interact....
Nov 8, 2024
3 mins
The new dialog element streamlines the implementation of accessible dialogs, modals, and other kinds of non-modal dialogs....
Oct 25, 2024
4 mins
Ever messed up a commit? Learn how to undo it like a pro! Our new blog post breaks down the git reset command, helping you navigate those "oops" moments with confidence....
Oct 18, 2024
2 mins
