84 karma · joined September 16, 2020
Formbricks: In-product micro-surveys
Analog: Fullstack meta-framework for Angular applications
Atri-Labs Engine: TeamStack for faster Progressive Web Apps development
HTMX: AJAX & Web Sockets directly in HTML
Code Hike: Build code walkthroughs for blogs, docs, slides & tutorials
Dioxus: React-like GUI library for multiple platforms, built with Rust
LinkFree: Connect with your audience through a single link
Seamly2D: Democratizing fashion design & production with Design CAD
Nbdev: Boost developer productivity with an exploratory programming workflow
Formbricks: Modular, customizable & extendable form functionality
Sniffnet: Cross-platform network traffic monitoring & analysis
Pypandoc: Thin wrapper for the universal document converter, Pandoc
Mockoon: Design and run mock REST APIs with ease
Nuxt Framework: Intuitive framework for building web applications on the edge
Responsively App: Accelerate responsive web page development
Datasette: Explore and publish data with this open-source multi-tool
Spyder: Scientific Python development environment
Strawberry: Python GraphQL library leveraging type annotations
Termux App: Terminal emulator for Android with 2000+ Linux packages
Poly: Fast Go package for engineering organisms
tRPC: End-to-end typesafe APIs made easy
What if engineers could build qualitative feedback into products right from the start?
In our experience, this often gets neglected because all dev attention goes to building the actual product. And yet, no one would launch a product without usage analytics because its insightful and really easy to implement.
How would a solution for qualitative data look like?
Formbricks aims to:
- fill the gaps between usage analytics and 1:1 interviews - keep dev attention at a minimum when leveraging best practices to gather qualitative data (Superhuman PMF, in-app interview prompts, onboarding & churn surveys, etc.) - build one user profile from waitlist -> paying customer (like early user CRM)
It's different from micro-survey tools because:
- doesn't clutter UI (natively embeddable in user flows) - specific analysis (e.g. for PMF survey) vs. generic visualisation of data - open source (self-hostable, freely customizable, embedabble)
The ask: Please poke holes in it :)
Happy sundays!
My key question is: Do you measure it to be able to optimize it?
We made a React Lib to make coding forms and surveys in React really fast and easy.
It comes with lots of prebuilt components for questions types and native Tailwind support.
We're adding non-standard types like star-rating, NPS, Slider, toggle out of the box.
We're also working on multi-step, form logic, internationalisation, accessibility and more.
Would love your feedback on the developer experience!
We took it out, I guess the less edge you offer these days the better off you are :)
Pricing an OS project isn't easy and we will introduce scaled prices per submission e.g. 500-2.000 -> 0,02$, 2.000-10.000 -> 0,01$ and > 10.000 -> 0,005$ or so.
We just didnt want to make it too complicated early on.
- free plan no CC needed (e.g. 100 submissions) - extended free plan with CC (e.g. 500 submissions) - paid plan with cost control (e.g. don't spend more than 25$)
Would that alleviate your doubts?