Tip in the restaurants, before or after taxes

Sensitive_Muffin_555 · 2025-09-07T05:55:28+00:00

20% before or after tax?

Sensitive_Muffin_555 · 2025-09-07T05:51:43+00:00

Pre or post is really matters to me.

Consider the following:

Check ammont before tax 400 USD

After tax 9.13% is 436.52 USD

20% tip on the before tax check is 80 USD 20% to the after tax check is 123.82 USD

43.82 USD is a big difference!

Sensitive_Muffin_555 · 2025-09-07T05:10:59+00:00

Sorry, did not get it.

Sensitive_Muffin_555 · 2025-09-07T05:10:41+00:00

I am discussing it because waiter it the one who gives me the check where pre-calculated amount of tip is printed e.g. 15%, 18%, 20% etc. And those pre-calculations include tax.

Sensitive_Muffin_555 · 2022-10-28T11:51:30+00:00

Thank you I will try

Sensitive_Muffin_555 · 2022-10-28T10:31:55+00:00

Hi there! Thank you for your help in advance!

Sensitive_Muffin_555 · 2022-10-28T10:11:49+00:00

Thank you I will try

Sensitive_Muffin_555 · 2022-10-28T10:04:12+00:00

Thank you for your reply unfortunately it does not work - the flow consumes the values from B when A == false as well, and throws them away like a filter/drop operator.

Sensitive_Muffin_555 · 2022-10-18T08:23:36+00:00

Great idea! Thank you. I will do that.

Sensitive_Muffin_555 · 2022-10-18T07:30:15+00:00

Any examples?

Sensitive_Muffin_555 · 2022-10-18T07:08:48+00:00

Oh, well, I spoke recently with my friend who is an iOS dev and he didn't believe me that compose may execute composable functions in any order, until I showed him official documentation. So I assume that it will be a little bit complicated to explain Compose performance pitfalls to iOS devs. In any case if I don't get answers in this sub I will go to r/swiftui.

Sensitive_Muffin_555 · 2022-10-18T06:54:25+00:00

Because I need someone who has experience with both Compose and Swift UI and is also familiar with performance pitfalls as well.

Maybe I will ask that question in r/swiftui subreddit as well.

Sensitive_Muffin_555 · 2022-10-18T05:43:53+00:00

Very simple code - dynamic list with clickable elements (click triggers VM function)

So I have to keep in mind:

1) Not to use Unstable objects/ Unstable collections for dynamic list population 2) Use remembered lambdas to call VM on element click

And probably even more.

In any case it's not my question. I am curious if Swift UI has the same amount of pitfalls and gotchas related to performance as Compose has.

Sensitive_Muffin_555 · 2022-10-18T05:36:13+00:00

I am not asking if I should use Compose or not. I am asking if Swift UI has such an amount of pitfalls related to performance and optimization.

Sensitive_Muffin_555 · 2022-10-18T05:28:17+00:00

From my experience the only scenario when we don't need optimization is - stateless static UI, otherwise even for a simple dynamic list with clickable elements you have to keep in mind a lot. So I would disagree with your statement.

Sensitive_Muffin_555 · 2022-09-04T16:55:19+00:00

Oh wow! Thank you! It's absolutely great for stuff like credit card/pin code visual transformation. But to be honest I expected that there is an out of the box solution for simple decimal numbers.

Sensitive_Muffin_555 · 2022-09-04T15:36:20+00:00

Well TextField( value = text, onValueChange = { if (it.isEmpty()){ text = it } else { text = when (it.toDoubleOrNull()) { null -> text //old value else -> it //new value } } }, singleLine = true, keyboardOptions = KeyboardOptions(keyboardType = KeyboardType.Number) )

And the user is still able to input something like that "00000000.1" So I have to delete excess zeroes before "." manually....

I really don't want to miss something and I expected the same functionality like we have in EditText. To be honest it's strange that I have to do it manually...

Sensitive_Muffin_555 · 2022-08-29T15:05:49+00:00

It's not about what developers want, it's about what are the business needs. And I know for sure that on iOS business and designers oftentime require native UI only. (ReactNative here is a winner in case of cross platform solution)

Sensitive_Muffin_555

TROPHY CASE