[Poll] What's the *biggest* pain point writing software for your App?
Caleb Jonas
12 replies
Replies
Mike Choi@guard_if
Praying for a timeline where I can write SwiftUI code that works on Android as well 🙏
Share
Having to develop and release for multiple platforms. Our application at Affordab.ly is available on 4 platforms. MacOS, iOS, chrome web store, firefox add-ons store, as well as our web app of course. We try to keep them all running the same latest release which means releasing and getting approval 4 times, testing and monitoring 4 times whenever we have a new feature. This can be extra painful if we have a bug. On our web app we can simply develop a fix and it will be deployed inside a minute. On our apps it can take hours to submit on the various app stores and often days to be approved and released.
@themon5ter All of the above! Yes we're writing in multiple languages. Swift for iOS, JavaScript for the browser extensions and a Ruby backend. It's for sure a pain having to manage all that. The biggest gripe though is testing and coordinating releases on several platforms. The browser extensions all use the same source code but all browsers have their quirks and things don't always work on them all, sometimes browser specific things are needed. IOS can be particularly difficult due to navigating their ever constantly evolving regulations. It's just a lot to keep on top of. Couple that with a slow release process and it can be a real pain point. I've launched things in the past that are just websites and this is very different.
The biggest pain point for me is making sure that the code I write is maintainable and scalable. I want to make sure that my code is easy to read and understand for other developers, and that it can handle any future growth or changes that my App may undergo.
@philipsnyder Are there any tools or patterns you use to help you make your code maintainable?
Having to develop for multiple platforms or browsers is always the biggest pain! Nothing worse than having something perfectly working on chrome and then switching over to test on safari and you find out its not supported!
@nathan_weinstock Does the support on Safari vs Chrome, have more to do with visual (e.g UI) issues? Or is it the feature set itself, e.g an API on Chrome for doing something like writing to a file (unseen by the user) not available on Safari? Do you have some examples?
@themon5ter I will usually try to look at the MDN web docs first before using any web api to make sure it is compatible across all of the browsers we want to support. With css I'm not quite as conscientious so it's often a visual bug that I wont notice until later.
For me is Justifying/finding the engineering time to build the same feature for each platform...Whether you want to learn more about personal finance or trade Stocks, Currencies, Commodities and Indices, Compare Brokers will help you.