arey_abhishek
Joined 19 years ago
Karma
497
Submissions
161
Member since
Aug 31
Founder of Appsmith.com open source project for building and hosting internal apps.
View on Hacker NewsRecent submissions
Comment · 1 year ago
Congratulations! This is such a great story. I’ve followed you for years and your success is inspiring
Comment · 2 years ago
Appsmith (https://www.appsmith.com/) | Full-Time | Remote (India) | Multiple Roles
Who we are: Appsmith is an open-source, low-code platform that helps engineers build enterprise applications quickly, usually within days. Since its inception, Appsmith has gained significant traction with over 10 million downloads, more than 30,000 stars on GitHub, and adoption by 10,000+ organizations across 150 countries.
We are hiring for work focused on performance improvements, developer experience and support engineering.
We’re hiring for the following roles:
Staff Backend Engineer Experience: 8+ years Link: https://wellfound.com/jobs/610609-staff-backend-engineer
Staff Frontend Engineer Experience: 8+ years Link: https://wellfound.com/jobs/3031540-staff-frontend-engineer
Technical Support Engineer Experience: 5+ years Link: https://wellfound.com/jobs/1921014-technical-support-enginee...
More roles at https://www.appsmith.com/careers#open-roles
Write to me at [email protected]
Comment · 2 years ago
I'm a founder of Appsmith, a well-known open-source low-code platform. We offer an alternative to tools like Outsystems, Retool, and PowerApps. I often meet people who share the skepticism about low-code seen in this post.
It's crucial to understand the advantages of low-code for specific situations, especially in developing internal applications. These tools, often neglected due to limited resources or developer disinterest, can be rapidly and effectively created with low-code solutions. Low-code excels in scenarios where internal teams are overwhelmed and business users face long waits for features. Although it's not a cure-all, low-code is highly effective for certain tasks where speed and ease are key, despite sometimes facing limitations in customization.
Some modern low code tools are also evolving to be closer to web frameworks. Plasmic is one my favourite examples of this.
Comment · 3 years ago
Does anyone have the code from the first commit?
Comment · 3 years ago
I appreciate your feedback and review. There's a lot of work to be done to improve Appsmith. It's still early days for this space.
Now, you mentioned that you found it painful to hook up APIs. Was it when connecting to multiple APIs or integrating the API response with UI components? Was it just using the online editor instead of a code editor? I'd love to learn more about the specific challenges you faced.
On the other hand, you mentioned that building something in React was a breeze for you. What aspects of React made it easier for you compared to using Low/No Code tools?
Comment · 3 years ago
Thank you for the compliments! I’m hoping we succeed and inspire others to choose a similar model.
Your story about the vendor is so commonplace. Paying for software only when it’s used makes so much more sense.
Comment · 3 years ago
Its just FUD then.
Comment · 3 years ago
I agree there’s a fundamental change, but saying that this change will lead to humanity’s extinction is exaggeration.
Show me one death because of AI before you can argue that 8 billion humans are going to die.
Comment · 3 years ago
The doomsayers look silly because they are extrapolating from 0 evidence.
Humanity is not going to end because of an online bot that can summarise and string words into sentences. It’s basically a smarter SIRI/Alexa. I mean the internet is not a ‘real’ place where humans live.
Comment · 3 years ago
Hi HN readers,
I’m the CEO and co-founder of Appsmith. Appsmith is a 2020 open source project that aims to be a quick way to build apps that talk to multiple data sources. People use Appsmith when they need a CRUD app or an admin panel or a complex internal enterprise application. We are an open source alternative to Retool.
It’s hard enough to build a business model around an open source project and getting the pricing right is a critical step. So today, we’re announcing usage-based pricing for all Appsmith customers. Appsmith Business now costs $0.40 per hour per user, capped at $20 per user per month. The self-hosted community edition is still, of course, free and open source, and we still offer the Enterprise edition with custom pricing.
We strongly believe that user-based pricing, which most of the SaaS industry and most of our competitors use, is unfair to the customers, and that usage-based pricing is a much fairer alternative.
When it comes to coming up with the right price for using software, tech companies have traditionally leaned toward user-based pricing, where customers pay based on the number of people who have access to the software from their team or “workspace”. The truth is, user-based pricing tends to artificially limit the number of users who can experiment with the software, can lead to wasted resources, and therefore carries an awful lot of hidden risk for customers.
But we propose that there is an already-proven alternative! In fact, “adoption for usage based pricing has doubled over the past four years.” (https://openviewpartners.com/blog/state-of-usage-based-prici...)
We have seen a highly successful wave toward usage-based pricing in the tech industry from AWS to Snowflake that can and should also apply to internal app builder companies in order to create a better experience for developers and open the doors wider to continued innovation.
When we first started testing usage-based pricing eight months ago, internal app builder companies were still in the user-based phase (the overwhelming majority still are), including well-known names like our biggest competitor, Retool. As a result, Retool has no choice but to try to sign large enterprise contracts with the pricing locked up before the user sees any value. The prices range from $25,000 to upwards of $100,000. User-based pricing is an approximate way of measuring usage and value, but it’s simply not granular enough to accurately gauge the customer’s needs. They are paying for seats that never log in and Retool isn’t able to spend time promoting more usage and a better developer experience because they must move on to the next sale. We see this as a huge inefficiency in their pricing model that ultimately ends up being unfriendly to customers.
Software should exist to enable developers to create and innovate, not make them feel unfairly exploited. While we believe that usage-based pricing is definitely the right way to achieve that, we would love to hear from our community and beyond - what is the fairest pricing structure for software in your opinion?
Comment · 4 years ago
Thanks for confirming.