9 ms·
> What does this app do on phones? On tablets? On laptops? The same thing, by default. Scale pictures and text automatically. <img src="some-image.svg" style="
by dheera 9y ago
> What does this app do on phones? On tablets? On laptops?
The same thing, by default. Scale pictures and text automatically. <img src="some-image.svg" style="width:0.1cm;height:0.1cm"> for universal compatibility without those godawful hdpi mdpx xxhdpi qxfhdpi directories and whatnot. Use something like CSS3 selectors or code if you want different layout on phones/laptops/tablets. The default should be to just display the same thing. Different layouts usually happens several months into an app's development cycle, and that's only if they actually gain traction. For most apps, targeting only phones is plenty good.
> Where is the header bar (the original has one, yours doesn't).
There isn't one. If you want one, add it:
<header-bar style="background:#ff00000;color:#ffffff">
Hello World
<hamburger id="mHamburger" style="float:right;"/>
</header-bar>
> What color is it?
The default, unless the developer styles it otherwise.
> What font?
The default, unless the developer styles it otherwise.
> What placement?
Left, unless the developer styles it otherwise.
> What about users who don't read English?
Don't worry about it and just display the text. When I have enough traction in my initial market, be that English or Japanese or French, I'll consider internationalizing later. Until then, everyone gets the same thing. In a lot of apps, until the content being offered for consumption is internationalized, it makes very little sense to waste time internationalizing the UI. And even if your app doesn't offer any content it probably still makes more sense to build and ship quickly (read: make building easy!) and worry about internationalizing later.
> What about users who's languages don't fit in ASCII.
Just default to UTF-8 already for all source files. End of story.
> Some poor souls at Google waste a lot of time making sure developers get a large library of useful layouts and controls that all mostly-just-work mostly-consistently across a huge spectrum of devices and API releases.
Great! I appreciate all that. But they should live on the system. An full-blown HTML5 app can be a few tens of kilobytes and support RTL languages and everything you mentioned. Chrome takes care of all that consistency stuff. Android should do the same for native. I shouldn't have to go through hell just to draw a button on the screen.