an application wrapper – which would likely be a stripped-down custom browser anyway – is definitely a feasible alternative, and it’s something i’m still considering for the future.
but the browser seems optimal with the existing feature set, for three primary reasons:
-
a wrapper does not allow you to use enough side by side with other tabs, where you are likely to be doing research or using other web-based editors
-
a wrapper would make enough less transparent and potentially limit configurability
-
using web browsers for ui rendering (which they are great at) drastically simplifies the codebase
also, i reckon most potential users have already installed and gotten comfortable with Safari, Chrome, or Firefox.