Matcha – A framework for building iOS and Android apps in Go

Re:Matcha – A framework for building iOS and Android apps in Go by wkrause on Tuesday October 03, 2017 @01:09PM (#15393993)

I'd start even simpler and use a tool like Figma to prototype the UI and workflows that are at the core of your app. Then start actual development based on the feedback from showing it to potential users.

A lot will depend on why you need cross-platform support at launch. For most direct to consumer apps, your intended user base should skew to one platform or the other and should be large enough to support a beta and launch on a single platform. Not launching with both platforms supported won't make or break your app and launching with both without much mobile experience to begin with could even prove to be a distraction while you try to iterate on you're app's design.

If you're selling an app to businesses, then not supporting both iOS and Android at launch would be a real roadblock. In that case starting and maybe even staying with Ionic could make sense.

[ Parent | on HN ]

Re:Matcha – A framework for building iOS and Android apps in Go by bogomipz on Tuesday October 03, 2017 @01:18PM (#15394090)

Thanks, yeah I am looking at a B2B project right now. Given that, is there value in using Figma as a first step or would that be redundant?

[ Parent | on HN ]

Re:Matcha – A framework for building iOS and Android apps in Go by wkrause on Tuesday October 03, 2017 @03:04PM (#15395092)

My only recommendation would be to not skip the prototyping phase, even if it's just a pen and paper. No matter how fast you are mocking things up in html, you'll almost always going to be faster sketching it out. When I started mobile development for the first time, I jumped right into coding and I feel like I wasted a lot of time re-arranging things I could have avoided if I just took the time to sketch it out.

[ Parent | on HN ]