That's probably true for calculator. But if you need some aside application for communication (e.g. Slack, Skype, whatever) accompanying your main workflow then it is better if that will consume as less resources as possible.
But even for more or less feature rich calculator, e.g. something like personal accounting/finances utility, you'd better have flexible UI.
Re:Flow browser passes the Acid tests
by fabiospampinato on Saturday June 13, 2020 @10:36AM
(#23509652)
> then it is better if that will consume as less resources as possible.
Which would automatically mean Sciter would not be a good fit for this.
> you'd better have flexible UI.
If that's more important then why not going with proper web technologies?
If making a calculator with web technologies is more important to me than making a very resource efficient one why would I _ever_ use Sciter for this that doesn't give me not proper web technologies to use and neither an actually resource-efficient calculator?