Store App Customization

Ragingmoomoo

Hi @Saurabh. Is it really not possible for you to make a tiny change in the js source of the store app to display item comments? (item.comment) { display it } I've done the work to have each item have its own comment box as having just one at checkout is extremely bad UX.

This minor change will not have any effect on your current customers and you can revert back to the original after you create the .aab file if you wish.
Please take this into consideration as the work has already been done and this change would only take minutes to do.

Saurabh

Ragingmoomoo having just one at checkout is extremely bad UX.

Swiggy, Zomato, UberEats all have the same "bad" UX?

Ragingmoomoo

Saurabh UberEats does not do it that way. The other 2 are Indian companies, so it seems to me it's an Indian thing - maybe Indians don't customize their food as much or aren't as picky. Check out any other big players from different countries and you'll see that the one comment box isn't the common way. In fact, I don't know of any that do it this way outside of India.

But let's talk about it. In what way is the current way best for UX? Say a customer orders 10 different items (is that common in India?) and they want 7 of those items with no salad, or salt, or whatever. The customer would have to enter the names of each item that they wanted to customize separately followed by "no salt" etc. into the checkout box. Then the restaurant would have to read back and forth as they entered the order into their POS system to match the changes the customer requested. What if the restaurant is super busy? What if the order in which the customer entered the comments also doesn't match the order of the items ordered?

What if the customer wants to leave comments for the DELIVERY side of things (which is where the checkout box is usually used), such as ""leave on doorstep"", ""gate pin is ####""? Having them being entered in the same single box as item customizations makes no sense and will just clutter things - the restaurant doesn't need to know about them.

Compare this to having the customer enter the comment as they are adding items to the cart, instead of all at the end. The comment will also appear under the item for the restaurant to easily see so it's not a giant wall of text as it currently would be.

I could understand if your reasoning for not implementing it was because you're busy and have other things to do, and I understand Foodomaa is based off Indian ordering and there are obvious cultural differences.
But to say that having one comment box for everything is good UX baffles me and I would love to hear your explanation of why you think this and what would be so bad with having comments under each item?
And just to reiterate, I'm not asking you to implement it, just to display it, as the work as already been done on my end.

Saurabh

Ragingmoomoo I am not telling whether it will be bad or good.

I understand your argument, but on a product level, it's not "easy" to implement simple feature like this.

There are literally 10+ places where this needs to be configured to work with Foodomaa.
If you want me to explain it why it would take time, do let me know, I will tell you how difficult is to implement a simple looking feature like this on a product like Foodomaa.

(Things are totally different if you are just implementing it on your own website)

Ragingmoomoo

Saurabh Your response of

Swiggy, Zomato, UberEats all have the same "bad" UX?

made it sound like you agreed with the current way it's done and it's good UX. But glad to know you don't.

I understand your argument, but on a product level, it's not "easy" to implement simple feature like this.

Like I said, I'm not asking you the implement this feature, as I have already done it. All that needs to be done is have the JS look for the field on the orderitem and if so, create an html element to display it. I understand that you're limited mostly by the fact that you cannot test it since your server won't return the comment.

Can I ask why you're keeping the source private?

Saurabh

Ragingmoomoo source is not private, you can get the full source by purchasing the extended license of Foodomaa.

Ragingmoomoo

Saurabh I'm referring to the store app. The changes I made work fine on the dashboard as I had the source. However, will not work on the store app as I don't have access to its source. Or am I missing something?

Saurabh

Ragingmoomoo Yes, the source for any android app cannot be released as it gets distributed all over the internet. (piracy)

joilson007

Saurabh Sir, I understand, but with the app source we would have the possibility to make some customizations.

Ragingmoomoo

Saurabh Here's the thing. As I mentioned above, Foodomaa is built upon Indian food ordering with many of the features copied from the Indian big players. Many of those features have very bad UX, 1 of which I have mentioned, or are just useless for other countries (such as the $x for two). But that's perfectly fine, because I had the option to buy and configure the source so I could change things. Having access to the source was a very big reason why I bought into Foodomaa, and I assumed this would have continued with future releases of products.

Now you decide to keep the source of your apps private citing piracy concerns. Placing DRM on your products only harms your customers more than it protects your software. All DRM can be broken - including Foodomaa and Ioncube. If people want illegitimate access to your products, they will get it. Surely you must have a list of customers you could trust at the very least?
Now I'm basically forced to use an app which isn't really up to standards (which I understand because it's your first app of the sort) and have no way of changing it.

You could just tell me to use something else but while there are shortfalls, there are also many great parts about Foodomaa, and the shortfalls could be changed. I really urge you to consider making the source not private purely because you're afraid people will steal and redistribute it.