HN Explorer

30 comments

[ 1.9 ms ] story [ 76.5 ms ] thread
amseun
Will appreciate your feedbacks and answer your questions. Thanks
pj4533
Some of the UI looks involved (like the chat UI). Much more complicated than other SwiftUI I have seen so far. I haven’t dug into SwiftUI at my day job, but would love to hear more details about your process. What issues did you run into? Did you use many third party dependencies?
jondwillis
I worked on a chatbot interface using SwiftUI for my previous job, I can semi-recommend this as a starting point: https://github.com/EnesKaraosman/SwiftyChat

There were several issues that arose from underlying changes made in SwiftUI between iOS 13 and 14.

You can always use UIViewRepresentable as an "escape hatch", but it invariably adds some complexity.

jmkni
How did you find SwiftUI?

I built a project with it recently and liked some aspects of it, reminded me of working with WPF years ago, but also found it a bit cumbersome.

amseun
Mixed. Some simple stuff with UIKit can be messy and complicated with SWIFTUI. But the intuitiveness of SWIFTUI will make you comfortable with some of the little challenges it poses.
bartvk
Minor spelling thing; I think it's capitalized SwiftUI, not SWIFTUI.
amseun
Smiles. Thanks @bartvk for the correction. I mind it the next time. Please of you you created a team on Kwayet I will glad to give your team blue-check. just let me know
ricardobeat
That "before the company begins to doubt your competency" message in the last screenshot is not exactly giving me warm fuzzy feelings about the app :)
amseun
Smiles. Not to worry. It's just a screenshot for a sample use case.
hdjjhhvvhga
On the other hand, the heading says "Tell your peers...". The person who wrote the message below is definitely not my peer - they're either my boss or my sworn enemy.
notimetorelax
They may be your best friend, sometimes you need someone to tell you this.
[dead] amseun
Smiles. Will use a more appropriate word next time. Thanks
alfonsodev
Congrats! it looks great!! Few questions if you have the time:

- How long it took?

- Was your first project in Swift UI?

- Was enough with Apple documentation?

- What other educational resources did you use to find how to solve the problems?

- What versions of Swift / Swift UI did you use?

amseun
- How long it took? About 13 Months

- Was your first project in Swift UI? Yes

- Was enough with Apple documentation? Not really. You will need some help on STACKOVERFLOW

- What other educational resources did you use to find how to solve the problems? https://www.hackingwithswift.com, asking and looking for a lot of workaround on STACKOVERFLOW

- What versions of Swift / Swift UI did you use? Swift 5.1 > SWIFTUI 2.0

yakubin
dang, I think HN automatic bot detection for new accounts kicked in for amseun (the dead comment). :/
amseun
Not now please.
saagarjha
Don’t worry, I went through and vouched for your dead comments.
amseun
Thanks so much @saagarjha am very grateful. Please if you created a team on Kwayet I will be glad to give your team a blue check.
amseun
just let me know in-app. Go to Phone -> Outsider -> Add New, enter this Kwayet-ID hello@kwayet
jehhjq
Would you say that swiftui is ready for complex production apps?
amseun
Absolutely YES. You can try out Kwayet and see for yourself.
jamil7
If you're able to target upcoming iOS15 I'd say go for it, I think a lot of people will jump on in this years iteration. I've been working with it since it's announcement and am now on a team building multiple products around it. If you need to build a complex macOS app I'd say stay far away for now but for iOS it's shaping up really well. Expect to use UIKit for some of your UI.
amseun
Please if you created a team just let me know. I will be glad to give your team a blue check. Just chat me up in-app. Go Phone-> Outsider -> Add New use hello@kwayet
maxpanas
Great stuff, looks fantastic! Congrats and good luck on the launch!! Everyone here is asking about SwiftUI :) I want to know what your backend looks like if you have the chance..

  - What DB are you using? (more than one? or just the one?)
  - Did you build an API layer - what did ya use - how was the experience?
  - Where are you storing uploaded assets?
  - Where is your backend (API, DB) deployed - do you use any tools to manage that?
Thanks! All the best :)
amseun
Used Node.js for the API layer Used Google Buckets to store Assets Deployed on Google Cloud. Used mostly Google Tools except for Twilio SendGrid for Transactional SMS.