shinyMobile is built on top of the latest framework7 template (V5.1.3). It may be used for different purposes:
shinyMobile has 3 skins:
It is possible to apply the iOS skin on android and inversely, even though not recommended.
shinyMobile brings 3 out of the box layouts:
f7SingleLayout: develop simple shinyMobile Apps (best choice for iOS/android Apps)
f7TabLayout: develop complex multi tabbed Apps (best choice for iOS/android Apps)
f7SplitLayout: for tablets and desktop with a sidebar, navbar and a main panel
shinyMobile has its own custom input widgets with unique design for each skin (iOS/android/aurora):
f7Stepper(): equivalent to
f7Button(): similar to
f7Button()with ability to be gathered in a
It also has custom update functions to act on the server side:
shinyMobile has custom input values tabs as well as dedicated update functions to act on the server side:
shinyMobile has custom input for sidebar (
f7Panel()) as well as a serve side update function:
Finally, it also provides tools to dynamically update widgets on the server side like cards, accordions and more:
This choice is crucial when you are developing an App. It depends on the complexity of your visualizations and content. If your plan is to develop a simple graph or table, you should go for the
f7SingleLayout() option. For more complex design, the best is
f7SplitLayout() is specific for tablets and desktop apps.
f7SingleLayout( ..., navbar, toolbar = NULL, panels = NULL, appbar = NULL )
While only the navbar is mandatory, other components such as the toolbar are optionnal for the
f7TabLayout( ..., navbar, panels = NULL, appbar = NULL )
The … argument requires
f7Tabs(..., id = NULL, swipeable = FALSE, animated = TRUE). The id argument is mandatory if you want to exploit the
f7Tabs() expect to have
f7Tab(..., tabName, icon = NULL, active = FALSE) passed inside.
It is the main skeleton of the template.
This is an option if you decide not to embed a
f7SubNavbar(). The toolbar is the rigth place to add
f7Badge()… Its position is controlled with the position parameter (either top or bottom).
Panels are also called sidebars.
f7Panel() is the corresponding function.
Although the App has a theme parameter,
f7Panel() has an independant theme option. For instance, it is definitely possible to create a dark
f7Panel() while the page theme is light, and conversely. Its behaviour is controlled via the effect argument: - “reveal” will make the body content move and resize - “cover” will cover the body content The resizable argument allows to dynamically resize the panel.
Note that for the moment, there is no option to control the width of each panel.
As stated previously for the
f7Panel() may also be considered as a sidebar. In that case, we may include
f7PanelMenu(). Finally do not forget to set up the
f7Navbar() so that panels are allowed!
This is probably the most inportant function of the template:
f7Init(). This functions helps to set up the template as well as properly initializing the main view of your app.
As stated above, you may choose between 3 skins and 2 color themes. There is a third option called “filled” that allows to fill the navbar and toolbar if enabled. The color options simply changes the color of elements such as buttons, panel triggers, tabs triggers, … shinyMobile brings a lot of different colors. hideNavOnPageScroll and hideTabsOnPageScroll allow to hide/show the navbar and toolbar which is useful to focus on the content. The tapHold parameter ensure that the “long-press” feature is activated. framework7 has more options which will be implemented in a next version of shinyMobile.