Common MVP features
hey guys, what are the most frequent technical features / requirements that keep recurring in MVPs?
I'm talking about things like: file uploading, user management (authentication, signing up) etc. .
I'm asking because I plan to build a solution that bundles these together.
It’s true that the bar is higher today than it was a few years ago. Users expect more. And that makes MVPs harder because you need to trade-off on some things.
I would ignore user signups and just create some kind of unique ID in the background and save yourself the hassle of auth flow.
Caching and making network calls between UI and backend fast is important. Users don’t want a long loading animation. Either pre-load your data or come up with tricks to make it look as if the data needed is already on the device.
Analytics is a big one that all MVPs need. You need to track exactly how users use your MVP from day one.
UI components that are easily customisable would be super useful too.
Hook that up to some caching/pre-fetching API lib plus seamless user identification and killer out of the box analytics and you’re golden.
To summarise your suggestion - performance is one of the best features, which I 100% agree.
Haven't thought analytics is so important, so I'll definitely raise the bar there.
Thanks!
How do you do in-SaaS analytics?
Right now I use Fabric.io because it was fairly easy to integrate. But I've started to also track events into my own database for flexibility.
These analytics companies hoover all the data from your users but only surface what they think is important to you.
Nice idea. I've helped a few clients do the design for their MVP's, below are some of the features recurring quite often in MVP's.
-User management
-Forms
-Social media integration
-Analytics
-UI components
-Creation of error pages (but not mandatory)
-Viewing data for non-devs (usually, the non-devs require the devs to update/view data and take action)
-User actions log (when users signed up, how often have they been using the product etc). Product owners can use this information to send targeted emails to users.
-Hosting
Great suggestions. Thanks!
I think you should also consider mailing system and payment solution integration (specially for Saas).
yep, both are part of the plan, although it won't be a SaaS.
This comment was deleted 4 years ago
Yep, and it makes sense. I plan to do it for JavaScript, more exactly: node.js and react.
The node.js ecosystem is different than the other ones. Ruby has rails, PHP has laravel and symfony, elixir has phoenix etc. - all these are great frameworks with quality extensions and building an MVP on top of these can go pretty well.
On the other hand, in node.js there are a few great frameworks, but none of them is as complete and well composed as rails or laravel.
But node.js kicks ass because is based on javascript. Managing assets with webpack comes naturally, the same for using GraphQL, doing SSR (server side rendering) of your client side app etc. .
I'm not planning to build the laravel of javascript, but to put together recipes (through well designed modules) that you can use when building an MVP with very less effort.