|
|
|
|
|
|
by ezrider4428
5725 days ago
|
|
|
In this situation the details are actually important. What 2 technologies are being used? Can you cross-train? can you hire more dev's on tech A? Which platform is more sustainable, scalable? What is the pool of talent in your regional area? Are you in the enterprise market or consumer market? Are you integrating with your clients via some kind of API or is it a SaaS model? All these questions impact your decision. It seems like you are only thinking about the technology but if you are a technology company then choice of platform has wider impacts. |
|
|
The backend of the app is PHP, and it already has an API. The front end is Adobe Flex. The rewrite would involve dumping Flex for a HTML/JS approach.
We initially went with flex because our app is quite rich in interactivity, but we could do the same thing in JS now.
It's not an enterprise play, but it is B2B. We could cross-train, but hiring more tech's for Flex would be expensive and hard to do (not a lot around). It is a SAAS model, so my customers don't care at all what tech I use (unless they are a tech firm, at which point they screw up their nose at Flex). But they don't mater, as they are not our target market.
Essentially, changing to JS would double our speed of dev in the last 8 months of the runway. But, it may take longer to do than we expect and we may cut off too much runway to make it worth our while.
It may be better to stick with Flex to the point of cash flow positive....then rewrite.