6
October
2021
Product

$10.5mn Funding Raised in Seed and Series A: How We Got Here and Where We Want to Go

0
 minutes

Appsmith launched a year ago, and since then, we’ve seen tens of thousands of engineers make Appsmith a part of their internal tooling tech stack. We’ve seen a lot of community contributions that have made Appsmith better for everyone

Today, I’m thrilled to announce that we’ve raised $10.5mn across two rounds of funding from Accel, Canaan Partners, Bessemer, and others. 

We couldn’t have done this without the love from our users and support from the community. We aim to use this capital and make Appsmith the best choice for every internal software project.

Appsmith, as an idea and subsequently as a product, came out of a series of interlinked personal experiences. A few years ago, when I was building Mob Show, a mobile game, all I wanted was for our daily active players to increase. In two months, we went from zero to five thousand, and we were doing everything we could to double that number. We wanted growth. Sure enough, we went from 5000 to 120000 DAUs within a week! We should have been thrilled, but we felt overwhelmed and exhausted. Why? Because unprecedented growth comes with unprecedented challenges. Scaling at such a breakneck speed amplified the number of bugs and problems in the game. Customer support requirements grew by 30x, while our team size remained the same. This growth was hell. We found ourselves scrambling to build internal tools that would help us make sense of this growth. 

I’ve seen this before when I was running Gharpay, a hyperlocal e-commerce company, where we relied on at least ten complex internal tools. These included backend tools for delivery personnel to manage and track their orders, tools for the accounting team to manage reconciliation on a daily basis, and of course, customer support tools to ensure speedy resolution of service requests. In fact, Appsmith’s co-founder, Arpit (who was also Gharpay’s CTO) was responsible for building and maintaining these apps. 

My co-founder, Nikhil, has also experienced the side of growth that is not pretty. Things go wrong wherever they can. And things will go wrong. As the head of product at Eat.fit, Nikhil saw orders scale from 50 a day to 50,000 a day in a short period. Customers began to have negative experiences; orders would go missing, delivery partners couldn’t find addresses, and there were payment issues. If these experiences are anything to go by, it’s that internal tools are critical to the success of every business. Nikhil, Arpit, and I feel strongly about the state of internal tools and believe that they are the backbone of any company’s success - old or new. 

So if Nikhil, Arpit, and I were getting together to create something together, both logic and intuition have led us to the Appsmith journey. We started Appsmith with a simple goal: To help engineers build the best apps they can to help their teams while avoiding repetition and monotony. Frontend and backend development for simple applications have become incredibly complicated. It feels like we are building the same things repeatedly but just using different programming languages.

Appsmith is an open-source low code framework to help developers avoid repetitive work like modifying UI components, writing integrations, creating a login page, etc., and building beautiful internal apps.  We have worked hard to create a product that developers use at Swiggy, Dunzo, WazirX, and thousands of other beloved companies. This has also meant that developers, HR, Operations, Finance, Admin, Customer Success, and Management teams have saved thousands of hours and boosted their productivity with Appsmith! 

Over the past 12 months, we have kept a razor-sharp focus on helping companies develop custom software that talks to different data sources. And each new day has been spent refining the product, building community feature requests, preempting the needs of our users. 

Since our launch, we’ve shipped:
35 UI widgets • 15 data integrations • JS editor • Debugger • Real-time commenting • A 2 min docker container setup

We’re gunning for more; brace yourselves! The Appsmith team and their speed of shipping genuinely amaze me. 

What Will We Do Next 

We’ll be shipping much-awaited features like white-labeled apps, custom widgets, mobile responsive apps, collaborative real-time editing, integration with multiple SSO providers, custom authentication, audit logs, and server-side JS execution in the next few months.  We will also be improving front-end customization while ensuring snappy performance. So we will be building a lot of new widgets, adding more integrations, introducing dynamic height components, custom theming, and supporting custom CSS.

Overall, we will be focussing on five areas: 

  • Improving the quality and complexity of the frontend that can be built using Appsmith. 
  • Creating better coding and data integration experiences for our users. 
  • Putting more effort into integrating Appsmith in the software development cycles of engineering teams. 
  • Developing and shipping features specific to larger teams, such as SSO, audit logs, granular role-based access control, etc. 
  • Creating an excellent repository of learning resources and material like tutorials, guides, and templates so that users can learn how to use Appsmith faster. 

We are fully prepared to fulfill our promises, and I know that our stellar team has already started work! 

Welcoming our Investors 

We’re thrilled to have the best minds in the industry backing us. Accel led the seed round. Canaan Partners led the Series A round with Accel, Bessemer, OSS capital, and Prasanna Sankar, CTO of Rippling.

By the community, for the community 

Appsmith is a community product. Open source creates public goods that benefit a lot more people than proprietary products. I believe that low-code, combined with the power of open-source, is the way to empower businesses large and small. 

Before Appsmith, there was no open-source project that could build such custom internal tools and admin panels. There are many low code products, but we saw that no competitor was willing to reveal the source code, enabling engineers to contribute changes. I think buying proprietary software is like buying a car without an option to fix it. Open-source helps you make small improvements and changes to the software. We also saw that our competitors would only work with companies with large budgets and ignore the experiences of small teams or individual developers.

One of Appsmith’s users told me that volunteers use it in France to help new immigrants avail of government services and enable them to navigate their new life. Appsmith is a forever free open source project that has helped developers build for food banks, non-profits organizations, schools, universities, and government agencies. It’s immensely satisfying to support such users.

Before I end, I would like to take a moment to thank the entire team for building such a fantastic project in a very short time.

Without you, there is no Appsmith. 

Coming to this point was a lot of fun, and in many ways, it’s the first step towards a long road. We expect it to be rocky, but it will be fun as heck. 

$10.5mn Funding Raised in Seed and Series A: How We Got Here and Where We Want to Go

Appsmith launched a year ago, and since then, we’ve seen tens of thousands of engineers make Appsmith a part of their internal tooling tech stack. We’ve seen a lot of community contributions that have made Appsmith better for everyone

Today, I’m thrilled to announce that we’ve raised $10.5mn across two rounds of funding from Accel, Canaan Partners, Bessemer, and others. 

We couldn’t have done this without the love from our users and support from the community. We aim to use this capital and make Appsmith the best choice for every internal software project.

Appsmith, as an idea and subsequently as a product, came out of a series of interlinked personal experiences. A few years ago, when I was building Mob Show, a mobile game, all I wanted was for our daily active players to increase. In two months, we went from zero to five thousand, and we were doing everything we could to double that number. We wanted growth. Sure enough, we went from 5000 to 120000 DAUs within a week! We should have been thrilled, but we felt overwhelmed and exhausted. Why? Because unprecedented growth comes with unprecedented challenges. Scaling at such a breakneck speed amplified the number of bugs and problems in the game. Customer support requirements grew by 30x, while our team size remained the same. This growth was hell. We found ourselves scrambling to build internal tools that would help us make sense of this growth. 

I’ve seen this before when I was running Gharpay, a hyperlocal e-commerce company, where we relied on at least ten complex internal tools. These included backend tools for delivery personnel to manage and track their orders, tools for the accounting team to manage reconciliation on a daily basis, and of course, customer support tools to ensure speedy resolution of service requests. In fact, Appsmith’s co-founder, Arpit (who was also Gharpay’s CTO) was responsible for building and maintaining these apps. 

My co-founder, Nikhil, has also experienced the side of growth that is not pretty. Things go wrong wherever they can. And things will go wrong. As the head of product at Eat.fit, Nikhil saw orders scale from 50 a day to 50,000 a day in a short period. Customers began to have negative experiences; orders would go missing, delivery partners couldn’t find addresses, and there were payment issues. If these experiences are anything to go by, it’s that internal tools are critical to the success of every business. Nikhil, Arpit, and I feel strongly about the state of internal tools and believe that they are the backbone of any company’s success - old or new. 

So if Nikhil, Arpit, and I were getting together to create something together, both logic and intuition have led us to the Appsmith journey. We started Appsmith with a simple goal: To help engineers build the best apps they can to help their teams while avoiding repetition and monotony. Frontend and backend development for simple applications have become incredibly complicated. It feels like we are building the same things repeatedly but just using different programming languages.

Appsmith is an open-source low code framework to help developers avoid repetitive work like modifying UI components, writing integrations, creating a login page, etc., and building beautiful internal apps.  We have worked hard to create a product that developers use at Swiggy, Dunzo, WazirX, and thousands of other beloved companies. This has also meant that developers, HR, Operations, Finance, Admin, Customer Success, and Management teams have saved thousands of hours and boosted their productivity with Appsmith! 

Over the past 12 months, we have kept a razor-sharp focus on helping companies develop custom software that talks to different data sources. And each new day has been spent refining the product, building community feature requests, preempting the needs of our users. 

Since our launch, we’ve shipped:
35 UI widgets • 15 data integrations • JS editor • Debugger • Real-time commenting • A 2 min docker container setup

We’re gunning for more; brace yourselves! The Appsmith team and their speed of shipping genuinely amaze me. 

What Will We Do Next 

We’ll be shipping much-awaited features like white-labeled apps, custom widgets, mobile responsive apps, collaborative real-time editing, integration with multiple SSO providers, custom authentication, audit logs, and server-side JS execution in the next few months.  We will also be improving front-end customization while ensuring snappy performance. So we will be building a lot of new widgets, adding more integrations, introducing dynamic height components, custom theming, and supporting custom CSS.

Overall, we will be focussing on five areas: 

  • Improving the quality and complexity of the frontend that can be built using Appsmith. 
  • Creating better coding and data integration experiences for our users. 
  • Putting more effort into integrating Appsmith in the software development cycles of engineering teams. 
  • Developing and shipping features specific to larger teams, such as SSO, audit logs, granular role-based access control, etc. 
  • Creating an excellent repository of learning resources and material like tutorials, guides, and templates so that users can learn how to use Appsmith faster. 

We are fully prepared to fulfill our promises, and I know that our stellar team has already started work! 

Welcoming our Investors 

We’re thrilled to have the best minds in the industry backing us. Accel led the seed round. Canaan Partners led the Series A round with Accel, Bessemer, OSS capital, and Prasanna Sankar, CTO of Rippling.

By the community, for the community 

Appsmith is a community product. Open source creates public goods that benefit a lot more people than proprietary products. I believe that low-code, combined with the power of open-source, is the way to empower businesses large and small. 

Before Appsmith, there was no open-source project that could build such custom internal tools and admin panels. There are many low code products, but we saw that no competitor was willing to reveal the source code, enabling engineers to contribute changes. I think buying proprietary software is like buying a car without an option to fix it. Open-source helps you make small improvements and changes to the software. We also saw that our competitors would only work with companies with large budgets and ignore the experiences of small teams or individual developers.

One of Appsmith’s users told me that volunteers use it in France to help new immigrants avail of government services and enable them to navigate their new life. Appsmith is a forever free open source project that has helped developers build for food banks, non-profits organizations, schools, universities, and government agencies. It’s immensely satisfying to support such users.

Before I end, I would like to take a moment to thank the entire team for building such a fantastic project in a very short time.

Without you, there is no Appsmith. 

Coming to this point was a lot of fun, and in many ways, it’s the first step towards a long road. We expect it to be rocky, but it will be fun as heck. 

Square
Try Appsmith
Inline editing in the table widget, integration with Airtable, and more
2
August
2022
Announcement

Inline editing in the table widget, integration with Airtable, and more

Inline editing in the table widget, integration with Airtable, and more
Vihar Kurama
0
 minutes ↗
#
announcement
Announcement

In July, we squashed 102 of the peskiest bugs and shipped 34 top requested features over and above under-the-hood performance and usability improvements. There’s a new table widget that’s so much more powerful, an Airtable integration, and cleaner Google Sheets queries with 178 commits in 22 days just for that enhancement alone! You can tell we have got our ears close to you. Keep it coming, guys. We love it all, and we are always listening.

#BigThings

The swanky new table widget

Fact: Just 25% of you tell us who you are and how you use Appsmith. We are okay with that. We respect your privacy.
Assertion: Our usage numbers should be 4X more.
Inference: When we say the Table widget, ever since we launched it, has been used a crazy 820,000 times by 6,840 users, we actually mean it's been used a lot more and is second only to the Button.
Takeaway: Give it more love.

Introducing the new Table widget

Everything you asked for from the table and more is packed into this massive update. Here’s three that should make you sit up.

  • With inline editing, you can now forget about writing queries to edit data by cell, row, or column. You just get your data into the table and edit on the screen. We heavylift the queries, updating the database, and making sure it sticks–all behind the scenes. Clicksaver? Lifesaver? Timesaver? All three and more? We think so, too.
  • You know how you have always wanted to refer to custom column names more naturally than typing customColumn1, customColumn2, and so on in your queries? Yep. Done. No matter what the name of your column, reference away just as naturally as you name them.
  • Themes have been making apps pretty for a while, but Tables stayed rebelliously aloof from that prettiness. We have now made them fall in line with Themes, so if you want shades of blue and Roboto, you got it in Tables, too.

There’s a whole lot more that you are going to have to see for yourself.

Airtable integration, out in the sun

Our Airtable integration gave UI facelifts to the low-code datasource. It is now out of beta, ready for its moment in the sun.

Connect with a Airtable base in two minutes, and start building your apps without worrying about complex data workflows.

 

Auto-indent here to make a dent

On our latest version? Tried the JavaScript editor yet? No? Do that now and you don’t have to read on anymore. 

Oh, okay. You are still here. Fine. We will show you.

Automatically pretty code is pretty cool, huh? More about it here.

#UpdateThings

“Hide Error Messages, Hide”

Infuriating little things, error messages, that bring up existential questions, right? And when they showed up all the time, they got us to, “Frustrating!”. They don’t anymore, only showing up when a widget is visible and clicked.

“How much to upgrade?”

Got your Appsmithing going, but a paid feature’s in your way? Fret not, self-hoster. We got your back with a command-line feature that estimates your usage in thirty seconds. Click this and all shall be revealed.

Run any Appsmith branch locally

With something like ./scripts/local_testing.sh chore/local-testing, running any branch as a FAT container is a breeze. Make sure Docker’s installed and running, port 80 is open, and you add arguments if you don’t want to run the release branch.

Errors, alerts, and logs

Two new modules, logger.js and mailer.js now store backup errors and alert you to them—helpful to get you on top of the error and aid find-and-fix.

While logger.js is on by default, mailer.js needs appsmithctl backup --error-mail to get humming.

Just two of the many, many ways we got your back(up).

Moving Google Sheets to UQI 

Google Sheets is a popular data source. We didn’t dig up numbers, but you can take out word for it. UQI stands for Unified Query Interface and affords standardization for queries. Made sense to get queries to Sheets working better and looking neater, too.

#AsAlwaysThings

If wishes were fishes, round-ups would be essays. Wishes aren’t fishes. So, head over to v1.7.9 if you closed our Release Notes in-app pop-up one of four different ways—yeah, we are fixing it—and see What Happened In July Appsmith style.

Need a new datasource connected?   ||    Discord    ||    YouTube    ||    Twitter

Track and manage bugs effectively using Appsmith and Airtable
1
August
2022
Tutorial

Track and manage bugs effectively using Appsmith and Airtable

Track and manage bugs effectively using Appsmith and Airtable
Vidushi Gupta
0
 minutes ↗
#
tutorial
#
dashboard
#
announcement
Tutorial

Airtable is a popular choice for developers who want to manage tabular data easily. While it's easy to use Airtable as a backend, it can be challenging to build a custom UI from scratch. This is where Appsmith comes in. With Appsmith's native Airtable integration, you can create dashboards, CRUD apps, and internal tools in minutes.

In this tutorial, we'll use an Airtable base to build an issue tracker. We'll start by creating a database in Airtable and then importing our data into Appsmith and building on top of it using JavaScript. 

With this application, users can:

  • Connect to their Airtable base.
  • Add a new bug/issue
  • Update the existing issue
  • View the current bugs in the management tool.

Let's jump in!

Step 1:  Getting started

Create a new Appsmith App 

First, we need to create a new application in Appsmith so we can build it out.

  • Visit https://www.appsmith.com to create a new account or login in to an existing one.
  • Create a new application in your preferred organization and edit it.

Connect to Airtable

Now, we need to add your Airtable datasource to the app. In this case, we will clone an existing Airtable sample to provide our data. 

  • Create a new datasource by clicking ‘+’ on the Datasources tab from the entity explorer and then select Airtable.

  • Rename the datasource. Select API Key as the Authentication Type and enter your API Key in the input field. Hit Save.

  • Choose a workspace and a base in the dialog box and hit 'Create Table.'
  • Go to https://airtable.com/api and select the base titled 'All bugs and issues'
  • In the 'Introduction' section of the documentation, copy the Base ID (highlighted in green in the picture below)

  • Select the "Bugs and issues Table" on the left pane. Copy the table name highlighted in green in the image below.

Step 2 : Set up UI for the App

Wireframe

Here is the wireframe for what we are trying to create.

Including the modal that is used to add new bugs.

Create your widgets

Using the wireframe as a guide, create the UI for the application using the drag and drop editor. Here is a suggested process.

  • Choose a preferred theme from the Theme properties option in the property pane on the right.
  • Add a container widget with a text widget for your app's header.
  • Three (or as many as you like) stats boxes on the canvas to display essential statistics at a glance.
  • A container with a text, icon button, and list widget for showing a list of all the issues.
  • A container with text, button, select and list widgets for showing details of the selected issues.
  • A modal with a text, icon button, and JSON form widgets for adding a new bug entry.

Step 3 : Binding data on widgets

Listing records on the List widget

The list of bugs/issues should look something like this. In order to populate the data, create a new query and bind the results to the text.

  • Create a new query from the left pane which uses the Airtable datasource you created in the first step. Rename the query to getBase and choose the Commands to be List records. We chose this command because we would like to list all the bugs and issues in our app. Enter the Base ID and Table Name you copied in the steps above. 
  • Hit Run and you should see a JSON response generated which lists the records. 
  • To bind this response to the list widget, we would first create a JSObject that maps the fields from the records. Create a new JSObject and paste in the following snippet.

getAirTableFields: () => {
  return getBase.data.records.map((record) => {
    let row = record.fields;
    row["id"] = record.id;
    return row;
  });
};


  • In this JSObject, we get the response from the GetBase query, map the fields, and get the id for every row in the table. 
  • Bind the list with this data using  {{JSObject1.getAirTableFields()}}
  • For getting the bug name and the source, bind the text widgets within the list with {{currentItem.Name}} and {{currentItem.Bug_source}} respectively.

Getting details of the selected bug

When we click on an item from the list, we should populate the view container with details of the selected issue


  • In order to get details about the selected bug on the container placed on the right, we would just use the {{List.selectedItem.attribute}} for all the details you wish to display. For example, The bug title can be displayed using {{List1.selectedItem.Name}}, for Associated features write {{List1.selectedItem.Associated_features}}, For priority write {{List1.selectedItem.Priority}}. So on and so forth. 
  • For a closed/open bug field, use the ternary format to display the status. {{List1.selectedItem.Closed == '1'? "Closed": "Open"}}
  • To bind the attachments for the selected bug, write {{List1.selectedItem['Attachments']}} to bind data on the list widget in the right container. 
  • Just like binding the bug details, in the image widget enter {{currentItem.url}} in the property pane to display the image attached
  • Use {{currentItem.filename}} and {{currentItem.type}} to display the file name and type on the text widget.

Displaying statistics on the statsboxes

These statsboxes should help display important information at a glance from this database. As the number of issues grows, this will give us a quick understanding of the status.

  • In order to populate the statsboxes with statistics, we would create a JSObject function that maps to fields and then to Priority within the same JSON response and check if the value is High, meaning the priority is set to high. What we get in the response is our desired statistic. 

highPriority: () => {
  const high = getBase.data.records.map((record) => record.fields.Priority);
  return high.filter((currentItem) => currentItem == "High").length;
};

  • Bind this output in the text widget using {{JSObject1.highPriority()}}
  • In the very same manner, write a function and bind the output for the number of bugs labeled open and critical

Adding a new Bug/Issue

When clicking the button to add an issue, a modal appears with a form that creates a new entry. It looks like this:

  • Set the Modal to open on onClick of the icon button on the top right corner of the container on the left. 

  • Populate the JSON Form with source data by pasting the following.

{
"fields": { 
    "Bug Title": "",
    "Priority": "",
    "Assigned To":"",
    "Status": "",
    "Screenshots": [
      {
        "URL": ""
      }
    ],
    "Bug Description": "",
    "Bug Source": "",
    "Features Associated": "",
    "Created by": ""
}
}


You can customize the field configuration as per your requirement. Here’s what the JSON Form looks like https://www.loom.com/share/1087b1e8932846feaf3dd03e8b3bb780

  • To insert a new record, we’ll write a new query. 
    Create a new query and name it as InsertQuery. Choose the command to be Create Records. Add in your Base ID and Table Name. For the Records, bind the form data from the JSON form for every field. 

[
  {
    "fields": {
      "Name": "{{JSONForm1.formData.fields['Bug Title']}}",
      "Priority": "{{JSONForm1.formData.fields['Priority']}}",
      "Status": "{{JSONForm1.formData.fields['Status']}}",
      "Attachments": [
        {
          "url": "{{JSONForm1.formData.fields.Screenshots[0].URL}}"
        }
      ],
      "Assigned_to": "{{JSONForm1.formData.fields['Assigned To']}}",
      "Description": "{{JSONForm1.formData.fields['Bug Description']}}",
      "Bug_source": "{{JSONForm1.formData.fields['Bug Source']}}",
      "Associated_features": "{{JSONForm1.formData.fields['Features Associated']}}",
      "Created_by": "{{JSONForm1.formData.fields['Created by']}}"
    }
  }
]

  • We’ll make a new JSObject function to run multiple queries when the Add Bug button is clicked in the form

addBug: async () => {
  InsertQuery.run();
  getBase.run();
  closeModal("Modal2");
};
  • Now bind this function on onClick of the Add Bug button in the JSON Form.

Update fields of a bug

This query/button can help update the details of the bug. In this case, we update the priority and statuses. 

To update the priority and status of a selected bug, an Update Records query would be used. 

  • Create a new query and rename it as updateQuery. Choose the command to be Update Records and enter your BaseID and Table Name. In the records field, paste the following to get the selectedOptionValue of the select widgets

[
    {
      "id": {{List2.selectedItem.id}},
      "fields": {  
        "Priority": {{Select1.selectedOptionValue}},
        "Status":{{Select2.selectedOptionValue}}
      }
    }
]

  • Now, bind this query to run on onClick of the update button.

Final thoughts

And that’s it! You have your bug tracker application ready using Appsmith’s native Airtable integration 🎉

First, you created a new Appsmith application and connected it to Airtable. Then you created the UI for your app using the drag and drop tools in Appsmith. Finally, you tied the data from Airtable to the UI widgets. Your final app should look similar to this:

Please use this form to contact us if you have any template requests for internal tools that you need, and we will get to work! 

If you have any questions, contact us on Discord. You can also keep up with us on Twitter and YouTube.

Build Custom UI on top of Airtable data
25
July
2022
Announcement

Build Custom UI on top of Airtable data

Build Custom UI on top of Airtable data
Rishabh Kaul
0
 minutes ↗
#
integrations
#
databases
#
announcement
Announcement

Today, our integration with Airtable comes out of beta and is available for everyone 🎉! You can now build custom UIs and interact with applications built on Airtable, with minimal configuration.

While it is possible to use the default API interface to connect to Airtable, we wanted to make it easier for you to directly connect your Airtable account and create applications faster than ever. This new data connector introduces a number of features:

  • Integration located in the “Datasources” section
  • Connect to your Airtable account with either an API Key or a Bearer Token (OAuth 2.0)
  • Create queries to fetch, create, retrieve, update and delete data from a datasource using the Appsmith query editor. 
  • List command lets you display all the data from Airtable, and can also present data that has been filtered and sorted based on fields, records, time zones, etc. 

For details and information on how to use this new integration (with videos!), check out our Airtable documentation here. See it in action on our full tutorial here, where we build an issue tracker with Airtable as backend. As always, let us know what you think!

What’s a Rich Text element?

asdsadasdsa

asdsadasdsa

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

sfdfsdfds

dsfdsfdsf

adfkaldf

The rich text element allows you to create and format

sadadasdasdas dsada sadas asd ad

Static and dynamic content editing

  1. vdfgdgd
  2. gjgjg

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

swzdswxzdsw