September 2022 Summaries

ShareChat, India's largest native social media app, faced challenges with its internal tools due to rapid growth, which led to inefficient engineering and operations. To address these issues, product manager Akshat Bhargava implemented a strategy to improve internal tool development by creating a dedicated Tools Team to handle frontends while other teams managed backends. This approach initially helped streamline processes but eventually faced bottlenecks due to increased demand. To scale efficiently, ShareChat adopted Retool, a platform enabling end-teams to develop their own frontends quickly. This shift allowed for faster app development and reduced engineering expenses by 20%. The operations team, for instance, developed a Creator Ops Management app using Retool in just nine days, significantly speeding up creator onboarding by 20%. ShareChat now operates more efficiently, with more than 500 Retool apps developed, empowering teams to meet their diverse use cases and boosting overall productivity.

The tutorial outlines a process to build a tool for managing Salesforce leads using Retool and Sequin, an alternative integration path that leverages Postgres for better performance and avoids Salesforce rate limits. The guide walks through setting up a Salesforce account, creating custom fields, and configuring a two-way sync between Salesforce and a Postgres database via Sequin. It then details the steps to create a Retool app that allows sales teams to efficiently qualify leads, search, filter, and update lead status using SQL and JavaScript. The tutorial also includes instructions on populating the app's UI with lead data, configuring quick link buttons for external research, and enabling bulk lead updates directly from the app interface. The approach is designed to save time and reduce complexity by eliminating the need for SOQL or APEX, and by allowing seamless integration of Salesforce data with other data sources to enhance context for sales teams.

Retool has launched Debug Tools to enhance error investigation and debugging in its apps, now available for all cloud users and soon for on-premise versions. These tools offer developers a detailed view akin to Chrome DevTools, allowing them to trace data flow, identify component dependencies, and reproduce errors in the user experience. Accessible via a bug icon or keyboard shortcut, Debug Tools provide editors and admins with comprehensive error logs, stack traces, and the ability to run JavaScript directly from the Console tab to inspect app properties or execute API methods. The Timeline tab visualizes query runs to aid in debugging, while the State tab displays property dependencies, making it easier to understand why queries are triggered. Additionally, the Linting tab highlights JavaScript errors, facilitating direct access to problematic code sections. Early adopters have praised the tools for simplifying the debugging process within the browser environment, and further details are available in Retool's documentation.

Upon joining Retool, the author was impressed with the streamlined Salesforce setup led by Jonathan Krangel, yet noted the reliance on spreadsheets and other tools due to Salesforce's limitations in UI and reporting. They addressed these challenges by developing a sales forecasting app in Retool, which streamlined data collection and reporting, saving significant time weekly. The app provides more flexibility in reporting compared to Salesforce, allowing for customized and efficient data handling without extensive maintenance. It also improves Salesforce data integrity by integrating user-friendly notifications and alerts, encouraging accurate data entry. The Retool app reduces the need for multiple tabs and offers a centralized, dynamic interface for sales reps, enhancing user experience. This suite of Retool applications has become integral to Retool's GTM strategy, offering substantial time savings and operational efficiency, enabling more time for sales activities. Additionally, Retool has introduced Debug Tools to aid developers in quickly resolving errors within their apps, further enhancing the platform's functionality.

In this guest post by Cameron Archer, the author discusses how he replaced Google Analytics with a custom web analytics platform using JavaScript, Tinybird, and Retool, focusing on recreating the Google Analytics Content Drilldown view. Archer explains the process of capturing web events data and utilizing Tinybird's SQL Pipes to analyze and transform this data into meaningful insights, such as aggregated pageviews for subdirectories. The post elaborates on implementing a privacy-focused approach that avoids using session cookies and describes how query parameters and API endpoints were used to replicate the drilldown functionality in Retool. The final product allows users to explore visitor interactions with website subdirectories and visualize their performance over time, mirroring Google Analytics' functionality without compromising on data privacy.

Stored procedures in Postgres are reusable functions introduced in version 11, which differ from traditional functions by not requiring an explicit return value and allowing transaction control, such as committing or aborting transactions. They are invoked using the CALL keyword and are ideal for tasks involving multiple, interdependent SQL statements that should be executed as part of a single transaction, such as handling new subscriptions in an e-commerce application. The creation of stored procedures involves defining a name, arguments, and a body of code, typically in SQL or other supported languages like plpgsql, C, or extensions like Python. While stored procedures can enhance performance by executing complex logic within the database, they can also pose performance challenges if not written in SQL, as they become opaque to the query planner. They are particularly useful for ensuring data consistency and integrity across multiple servers or microservices that share database logic. The article discusses scenarios where stored procedures are beneficial, explores their performance implications, and offers guidance on creating, using, and altering them in Postgres.