Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
So quick crash course in desktop versus phone layout desktop layout is the exact interface that we've
been working with this whole time.
That's the default standard when you switch to a phone layout.
You'll see a view like this.
And what phone layout does is it allows you to design on a canvas size that's optimized for mobile viewing.
So important thing to note you don't actually do any building of content within the phone view.
You build in the desktop layout and then switch into phone view and kind of assemble your pieces and
resize within that new constricted canvas.
Now this really won't come into play until you start getting into power by service and publishing but
because it is an option in part by desktop I wanted to quickly cover it here.
So let's quickly whip up a mobile optimized version of our exact summary.
So by default we're in our desktop mode go to the View menu and click the phone lay out what it does
is it gives us this shrunken down canvas and assembles all of our pieces or components over here on
the right.
And that includes everything even these little icons that we dropped in slicers maps charts visuals
logos all of the pieces are here.
So as we start actually dragging items onto the canvas you'll start to see that we really don't have
much flexibility for sizing.
So we're not going to be able to get all of these elements into a mobile phone view unless we stack
them.
You know one on top of each other but let's try to get the most important things in here.
You know maybe it's the current monthly revenue.
Maybe it's the current monthly orders here.
Try to squeeze in returns as well.
Kind of a big KPI as we could probably show our subcategory view down here and stretch it out a bit
and why don't we pull our tree map that get I'll make it bigger.
It's kind of hard to work with.
There we go.
And maybe it's the top order product there as well.
So you know obviously you don't have to follow along with what I'm doing exactly but maybe something
like that makes sense.
And now when you switch back we haven't edited anything on the desktop view at all.
We've just created a new variation of it here in the mobile view and now if you do end up publishing
this report then it will become accessible on the power of the mobile app.
And this is how users will be able to see and interact with that report.
So there you go.
That's phone versus desktop layout.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.