![]() The user should have no way to reach the login screen without invoking the Logout function. From this page, if the back button is pressed the user leaves the app. Successful login or registration should place the user on main page. Pressing the hardware back button should cause the user to leave the app. ![]() The user should launch the app and if no valid authentication information is available, the user should be placed on the login screen. When the user launches the app and valid authentication information is available, the user is immediately placed on the main page. Upon successful login or registration the user should be placed into the app with no way back to the login screen without invoking a logout function. The user should launch the app and if no valid authentication information is available the user should be placed on the Login screen with access to a create login screen. Here is the story for each of the platforms: It is fairly standard paradigm where the user must login before being granted access to the app. However, one has to undertake significant effort to support even the most standard user flow in Android and Windows Phone.Ĭonsider a simple app with a login function that fronts the main app. On the topic of navigation, this is not done well in Xamarin.Forms and for Forms to be successful its going to have to be done better since Navigation is one of the core elements in a successful experience. Here is a link to the styles as generated by the website: Navigation Kind of weird, since one would think I should be able to do this via the Custom Rendering engine. [Activity(Label = "Score Predict", MainLauncher = true, Icon = class MainActivity : FormsApplicationActivity, IPageHelper The only way I found to correct this was to visit which allowed me to create a Style that I could apply to the MainActivity responsible for launching the application. I was trying to after this to fix Android which looked like this:ĭespite defining a Custom renderer for TabbedRenderer I could not get a reference to the TabWidget or the TabBar. It also seems like you cannot Custom Render the TabbedPage interface. ![]() It seems like this would be the preferred way forward, or at least allow the usage of the left hand side of the navigation bar. This was established in iOS7 and has become an integral part of many of Apple’s own apps, such as Maps: There actually is a precedent for handling this scenario is iOS, the toolbar. Generally, you get only two buttons with the left primarily be used for navigation. I dont recall ever seeing an iOS app putting two links in the upper right or left. Honestly, between the two the former is the better looking, but not by much. On iOS though you have two options: specify both as primary and get this: Secondary places the item directly into the overflow (application menu on WP and the pop out on Android). On Windows Phone and Android, Primary will make the action available outside the overflow until the space is consumed. At this point the team has settled on the concept of primary and secondary navigation. This concept is fairly straightforward in Android (Action Bar) and Windows Phone (Application Bar), but is less clear on iOS which has limited space in the Navigation bar. However, it is clear the team is still not sure what do on at least one element in iOS: the toolbar. Where you mainly run into issues is when applying a custom theme, but most of this can be solved with custom renders or by leveraging the abilities of the platform as in the case of Android. Achieving this would effectively negate the single biggest weakness of “one and done” platforms like Titanium and PhoneGap, which is allowing a single UI but creating one that follows the idioms of the target platform.įor the most part Forms nails this pretty well. The idea for Forms, conceptually, is very ambitious: unify the definition of the UI and allow each platform to translate that definition into a native user interface. Sadly, while there are many positives with Forms, certain features are weird or just not developed enough for me to give the platform a full vote of confidence and make me choose to use it over more mature approaches such as those involving MVVMCross. After much emphasis by Xamarin at their Evolve event in 2014 I wanted to get a sense as to how ready Forms was for primetime, especially with the recent 1.3 release. I have spent the better part of the last few weeks building my Score Predict app in Xamarin.Forms.
0 Comments
Leave a Reply. |