Discussion of article "How to Post a Product in the Market" - page 18

 
Y.A.K._:

Thank you, that's clear.

Now I'd like to understand if there is a limitation, because opponents say the opposite.

There is a limit on page length in the market. It was introduced not so long ago. Such a restriction is checked by a moderator.

Imho, the "Documentation" tab is really lacking for serious, infrastructural products.

 

Saw that. It seems that automatic checking was introduced just the other day.

I managed to prepare two drafts before that, now it pops up when I try to save even without any changes:

Размер описания должен быть от 300 до 3600 символов без учета пробелов

Yes, under these circumstances, documentation is going in the same direction as elephants.

Maybe add an optional "Documentation" tab?

 
Y.A.K._:

Could you add an optional "Documentation" tab?

The only question is who will translate it into several languages.
 

Please explain about dll.

Are products that use dlls at all (User32, Kernel32... )prohibited .

or only those with man-madedlls????

Thank you.

 
ALXIMIKS:

Please explain about dll.

Are products that use dlls at all (User32, Kernel32... )prohibited .

or only those with man-madedlls ????

Any DLL.
 
Renat:

We have no limit on the length of the description. Unlike others.

It doesn't look very nice, Renat. You're an official, but you're twisting the facts. I see you only want to deny everything, regardless of anything. In this way, it's pointless to have a dialogue with you.

The problem with screenshots you made up. You can always cut and show in a series of 640x480 screenshots what you need. To do this, you should not use the "Print Screen" button in full size, but select the necessary pieces for demonstration.

Usually authors do not realise that to demonstrate the idea 80% of the space of their screenshot is superfluous or filled with the wrong thing. All it takes is enough thought and it can very well be tucked away.

Well yes, from your words, all sellers of the mentioned Google and Apple are idiots who don't realise anything. What fools! wasting 80% of modern monitors' space by placing screenshots in HD (or FullHD) quality instead of cutting them into 640x480 (or better 320x240) pieces, and the user himself will put together a puzzle from them, what else should he do? And 80% of pixels of his FullHD monitor let them rest, why overstretch them.
 
Rosh:
The only question is who will translate it into several languages.
Then please advise me on specific examples(draft 1 and draft 2), what to leave in the description and what to transfer to the discussion.
 
meat:

It doesn't look very nice, Renat. You are an official, but you twist the facts. I see you only want to deny everything, regardless of anything. In such a way it's pointless to have a dialogue with you.

I'm sorry, I made a mistake.

There was no restriction before, but it was introduced some time ago at the request of moderators. But they forgot to write a message about the restriction next to the field.


Well, from your words all sellers of the mentioned Google and Apple are idiots who don't realise anything. What fools! wasting 80% of the space of modern monitors by placing screenshots in HD (or FullHD) quality instead of cutting them into 640x480 (or better 320x240) pieces, and the user will make a puzzle out of them, what else should he do? And 80% of pixels of his FullHD monitor let them rest, there is no need to overstretch them.

I didn't say idiots.

Here, by the way, the Google Play limit on the length of text 4000 characters. And there is no rich content, as Google does not want to fight for the design:

Google's screenshots can be uploaded big, as they have to show the whole screen face, not a small part (our programmes work inside the charts) like we do.

 
Rosh:
The only question is who will translate it into several languages.
Even now, MK doesn't bother translating product descriptions. For example, I publish the Russian and English versions, so for all other languages (Chinese, Spanish) the English version is displayed. So nobody has to translate anything - everything is left to the author. You could do the same with documentation. However, the option with a link from the description or discussion is fine with me too.
 
marketeer:
And even now, MK doesn't bother translating product descriptions. For example, I publish the Russian and English versions, so for all other languages (Chinese, Spanish) the English version is displayed. So nobody has to translate anything - everything is left to the author. You could do the same with documentation. However, the option with a link from the description or discussion suits me too.

When you publish in Russian, they translate it into English.

Perhaps when publishing in a language other than Russian and English - they translate into both.