Other Software > Developer's Corner

Quickly developed web application or slowly developed actual application?

(1/2) > >>

Tuxman:
What would you rather use and why?

I prototyped a new project (basically, a decision helper) in Javascript and ugly CSS and I need an idea if it would be worth the additional effort to reimplement it as native applications. (Platform-independent, of course.)

Ath:
Depends heavily on the purpose/goal of your application...

mouser:
I think you did the smart thing in terms of whipping up a quick prototype.  I think that is almost always the best first step.
So now that you've seen your prototype, is there enough reason to spend time making a more robust version?

wraith808:
Depends heavily on the purpose/goal of your application...
-Ath (April 21, 2018, 11:09 AM)
--- End quote ---

This.  So much this.  People look at web vs desktop as if it's a static decision.  It's very much based on use case, IMO.

Tuxman:
The use case is that I want an application which helps me throwing a dice to reduce my shopping list from 30 to 15 or so items. Basically, by randomizing the list. (With additional parameters like "low/high priority" and "price per item / total budget". But that's the smallest part of the code as of now.)

The major advantage of my prototype is that it's already finished. The disadvantage is that it requires Javascript. Or, more generally spoken, it works on almost every OS and device, but it could be more efficient in terms of general security (I'm not really a fan of Javascript, as you might see) and performance when written natively.

Navigation

[0] Message Index

[#] Next page