|
|
|
|
|
|
by saagarjha
2370 days ago
|
|
|
> If you want to make a product, use what ever tool is most productive for you. If you’re making a product that other people use, I would caution you against putting their needs on the back burner. It’s very often the case that what’s easier for the developer ends up making a worse product for the people that have to use it. > Unless you're writing an IDE, you're not going to lose users (you care about) over not supporting Emacs bindings. No, the whole point of this feature is that it works outside of an IDE. I don’t even use Emacs and these shortcuts are so ingrained in me that I ended up setting up custom shortcuts to emulate this in the places that wouldn’t support it (where possible, of course…). |
|
|
Unless you mean some of their needs.
In which case yes, that's my point. If you want a successful product, prioritizing features is very important, and in most contexts, filling your "core need" is going to add a lot more value than a native UI does.
>I don’t even use Emacs and these shortcuts are so ingrained in me that I ended up setting up custom shortcuts to emulate this in the places that wouldn’t support it (where possible, of course…).
Unless your tool is for a space where a lot of users are going to say stuff like this is a major detractor for your new product (...like an IDE or other developer tool) you're much better off just making your product and validating it.
-
When you're making a new product, and bootstrapping it like OP describes, your currency is time.
Time isn't just money, it's a changing market, it's your own motivation coming and going, your overall situation can change and make working on it untenable.
The less time you spend fighting a lack of knowledge the better.
A working MVP in Xamarin.Forms in a few weeks > months spent killing the moment for your idea and learning enough iOS and Android to have the base knowledge for a middle of the road native app, is true much more often than people like to admit.