What It Was Like to Write a Full-Blown Flutter App

Re:What It Was Like to Write a Full-Blown Flutter App by HillaryBriss on Saturday June 16, 2018 @10:13PM (#17330568)

there's a lot of enthusiasm, yet, i feel less enthusiastic about Flutter after reading this.

i had not thought about this right in the past. i hadn't factored in the reality of needing to maintain two separate UI trees, one with Material Design widgets and one with Cupertino widgets. this makes me think one of the really big advantages i thought Flutter had -- a unified UI -- is not really realistic.

i must be misunderstanding this

[ Parent | on HN ]

Re:What It Was Like to Write a Full-Blown Flutter App by seenickcode on Sunday June 17, 2018 @09:00PM (#17335254)

Hi there, I'm the author of the article. I'd like to clarify that it's not bad at all. Libs exist out there, such as offering a cross platform nav bar, seemless where you wouldn't have to maintain two separate codebases. Also for things like forms, if you have a custom design, you won't be having a lot of "if/else" statements, you'd simply use one set of widgets since they'd be custom.

[ Parent | on HN ]

Re:What It Was Like to Write a Full-Blown Flutter App by HillaryBriss on Sunday June 17, 2018 @10:12PM (#17335511)

Thanks for your clarification. I'll have to give Flutter a try some time.

[ Parent | on HN ]