1

If you were to start making a lightweight, fast, multiplatform client app, architecturally clean and simple, with as little of the JS(style) libraries and packages and transpilers and weird convoluted and/or unpleasant syntax trends like JS or flutter...

ideally (or at least minimally) something at least as straightforward as making a WinForms app in C#

...what language/tool/platform/tech stack would you choose?

...asking for a friend with totally not an absolutely cool idea that needs to exist.

Comments
  • 2
    I would avoid multiplatform stacks from the getgo, I've never had good experiences with them. Assuming you want web, iOS, and Android.
  • 0
    @ars1 yes, i want web, ios and android.

    okay, what would i use if i were to use... ehm THE FRIEND... what would THE FRIEND want to use if he was to use native-targeting stacks/platforms for Android and iOS, in that order of priority?
  • 1
    Which platforms?

    For the best dev experience, there is only native development.
    iOS: Swift + SwiftUI
    Android: Kotlin + Jetpack compose.

    For the web there is little hope for good dev experience but if you need it as a platform as well, you might use Flutter for web+iOS+Android.
  • 0
    There is also Kotlin Multiplatform.

    https://kotlinlang.org/lp/mobile/

    I haven’t tried it myself though.
  • 0
    If the app doesn't require direct phone integration (like accessing native phone API's) you could just start with a website (any tech you like) and commission someone to create native webview wrapper apps for android/ios. Or even more lightweight is a PWA (though not sure a lot of ppl spot the "Install" option)

    Eg I have this one installed as PWA: https://www.unitconverters.net, works flawlessly
  • 1
    @Lensflare no, fuck flutter with its stupid syntax and useless error messages XD
  • 0
    @webketje it does absolutely require phone notifications and running a background process
  • 0
    @Midnight-shcode just don’t tell your friend about that syntax and error messages 😆
  • 0
    @Midnight-shcode think there is a notification API in the browser, but bg process, yeah, will need to run native then
  • 0
    As far as the client is concerned, you might want to go with a vanilla js/html approach that fetches from localhost on a 1024+ port# that is served by a small native 'server' (java or whatnot) that acts as a simple communicator/facilitator for bubbling up native notifications.
  • 1
    @JS-Guy what the fuck is wrong with y... oh, i see your username, nevermind XD
Add Comment