Skip to Content

SAP Fiori Client

A while back, I wrote here about an application we were calling the Kapsel Enterprise Browser The application was demonstrated at TechEd to great acclaim. At the time I wrote that blog post, I knew what was going in, but couldn’t write it about it yet. Well, now I can!

The Kapsel Enterprise Browser application has become an SAP product called SAP Fiori Client, the mobile runtime client for SAP Fiori.

On mobile browsers, the web content files that comprise the application will be cached by the mobile browser; but they may be quickly purged (within several hours or sooner) by the mobile device – without the user’s knowledge. For SAP Fiori, subsequent loads of the application after the browser cache has been purged by the device will cause the full application assets to be retrieved again. Any performance benefit a user obtains from browser caching of application resources between sessions is lost when the browser arbitrarily, and potentially randomly, purges its cache.

The SAP Fiori Client uses the same multi-channel SAP Fiori web application, but users get more consistent performance through the enhanced cache management features provided by the application. The application, a native mobile app, built using the open source Apache Cordova framework, renders SAP Fiori application content, and provides more reliable asset caching (HTML, CSS, JavaScript files and more) plus, on iOS, an enhanced  attachment viewing process.

SAP Fiori Client implements a cache management strategy that allows the native application to maintain its own cache of SAP Fiori application assets. Therefore, the application is not affected by browser cache issues.  When the application runs for the first time, it will pull the SAP Fiori application assets from the server just as the mobile browser would. On subsequent loads, however, the application uses the local cached assets for the application. During operation, the application automatically detects when updates have been made to the SAP Fiori applications and, when an update is detected, will purge its existing cache of SAP Fiori application assets and pull the updated content from the server.

SAP Fiori Client performance will be comparable to the mobile browser on initial application load, and after an update has been made to the application; but at all other times it will operate using the cached SAP Fiori assets. The benefit for SAP Fiori application users is increased overall performance for application loads, as the periodic purge of browser content no longer affects SAP Fiori.

With the application, SAP Fiori users also get full screen operation as the SAP Fiori Client removes the standard mobile browser chrome from the window.


Figure 1 – SAP Fiori Client Full Screen Operation

A simple gesture, a double-tap on the screen for Android and a two-finger hold against the screen for three seconds brings up an options screen that allows users to quickly navigate to the SAP Fiori Home page, navigate to the previous page or refresh the current page. On Android devices, the menu also includes access the settings screen; iOS users access the SAP Fiori Client settings from the device Settings application.


Figure 2 – iOS Activity Menu


Figure 3 – SAP Fiori Client Settings on Android

On iOS, the SAP Fiori Client implements enhanced attachment handling capabilities that are more tightly integrated with the native application than is possible with current mobile browsers. When a user opens an attachment from within SAP Fiori, the attachment opens in a window which the user can close and immediately return to the application.

After the application is deployed to a supported mobile device and the application is first launched, the user is prompted to provide the endpoint URL for their organization’s SAP Fiori implementation. Once the user enters the URL, the SAP Fiori content is loaded and ready to go.

The SAP Fiori Client supports Android 4.1.3 and higher and iOS 6 and higher and is expected to be distributed through the Apple and Google app stores.

You must be Logged on to comment or reply to a post.
    • It's a native client application for Fiori.No, it does not require SMP. It will work with SMP, but does not require it. Our goal is to enable some additional capabilities through SMP, but not in this initial version.

  • Great news! So will the native app still work on SAP Netweaver Gateway alone, or will customers need the SMP 3.0 for all the Fiori mobile client functions to run properly?

    Thank you for sharing!


    • It is a native application for SAP Fiori. The cache management capabilities of the application are specifically engineered for Fiori and some capabilities that the Fiori application server exposes.

        • As I understand it, and I'm not an expert in SAP Fiori, a SAP Fiori app is a 'type' of app that is built using UI5 and other design principles. You build SAP Fiori apps using UI5, but you can build other apps using UI5 that are not SAP Fiori apps.

          The SAP Fiori Client has a specific understanding of SAP Fiori and can detect when SAP Fiori, and the SAP Fiori apps that run within it, are updated and act.

          • Thanks for the quick reply, John. Do you know of anywhere we could go for more technical information?

            yours thirstily

            Just Another Fiori Developer 🙂

          • It's a very simple native mobile application that provides the following:

            1. SAP Fiori web application asset cache management (eliminates performance issues that are caused by the mobile browser randomly purging its cache)

            2. Full screen operation for SAP Fiori

            3. More streamlined attachment handling on iOS

            That is really all there is to the application today.You start the app, configure the application for your SAP Fiori instance (type or paste in your organization's SAP Fiori URL) and from that point forward, the application manages the web application cache as SAP Fiori runs within it.

            What other information do you need?

      • Sounds good look forward to hearing more about this and how the applications works with the Fiori Applications, and how we as developers can build onto that.


  • Hi John,

    Thanks for sharing and I'll echo DJ here and say it would be superb to get some more technical info about all this.

    It seems to echo a bit of the Hybrid Web Container of old from SMP - although of course much improved as it does not have to be provisioned from the SMP server.

    For me the benefit here would not be the caching as with a properly implemented Fiori or Fiori-Like app you should be able to benefit from the built in cache-buster functionality to at least minimise that.

    No, for me the benefit here is the easily accessible launch-pad which could break that barrier to adoption by making it that little bit easier. I would have questions about:

    • Does it cache credentials
    • What about multiple back-end app sources
    • What kind of app-entry security is there (it may not be required based on q1)?

    Looking forward to hearing more about it 🙂



    • I think you're missing the point of this application.

      Cache buster (as I understand it) is designed to keep assets from being cached. By generating a unique URL for assets, it forces the browser to keep up to date content. The Sap Fiori Client does the opposite - keeps SAP Fiori assets that we are certain have not changed. That's where the performance increase comes from.

      Regarding your questions:

      1. Does it cache credentials? The SAP Fiori Client caches web application content. Not data, not credentials. The SAP Fiori client simply manages the cache of web application content.

      2. What about multiple back-end app sources? DId I mention that the SAP Fiori Client is for managing the cache of SAP Fiori web application assets. Back-end data sources have nothing to do with SAP Fiori web application content.

      3. Regarding app-entry securiry. Did I mention that the SAP Fiori Client is for managing the cache of SAP Fiori web application assets? It's for running SAP Fiori in a native app (with better cache managment than the browser and a few more features which I have already described in the post) - SAP Fiori provides the security as that's already a core component of SAP Fiori.

      • Hi John,

        Thanks for coming back to me. I think perhaps we are on different pages though - my questions around caching of credentials and security were purely from a usability point of view for end users who may be hesitant to adopt new technologies like this (especially in a BYOD scenario).

        My thought process was that if it were to cache credentials, it would be one less thing the user would have to do to gain access to the apps. But If i'm understanding you correctly the app will not be attempting to do this which removes the security question.

        On the multiple back-end's question - I wasn't really referring to the caching of Fiori assets, I am more talking about a company that may have two or more completely separate Fiori installations with completely separate launch pages so therefore would require two or more separate links - so can the application pull the list of apps available for a user from two different sources?

        Finally, on the cachebuster question (and I'm happy to be proved wrong on this) my understanding is that it is designed to facilitate notifying the browser to refresh it's cache of a particular resource only when it has changed (or after a year I think - whichever is first) - so the browser can indeed load a large proportion of the content from cache unless the server indicates otherwise. I'll be completely honest and say that I've not used cachebuster in anger yet but that is my understanding from what I have seen.

        Kind regards,


        • Brenton,

          I think we are on different pages. All this application does (almost all it does right now) is provide a more cache friendly experience for mobile users. Any caching of credentials would have to be done by SAP Fiori. Now, we plan on adding enhancements over time, but right now what it does is pretty simple and pretty powerful.

          Regarding the back-ends, the SAP Fiori Client is designed so you can configure it to point to one SAP Fiori instance. I've shown you the configuration screen - it allows you to enter a URL for your organization's Fiori Launchpad. As all it does it provide a more cache friendly place to run SAP Fiori, we're assuming that you as a user have one SAP Fiori instance you point the application to. We have not considered that a user would have multiple instances of SAP Fiori; we did talk about implementing something like that for demo purposes, let someone switch between instances, but that did not make it into the product.

          Doing that causes problems though as switching SAP Fiori instances or changing the SAP Fiori URL would invalidate the application cache and cause the site to reload. That breaks any benefit you get from having the SAP Fiori Client. If you have to reload everything every time, they just use the mobile browser.

          If people need this, we need to know, but don't imagine this affects a lot of customers. Please correct me if I'm wrong. Again, not a SAP Fiori expert, but with the configurability and tile assignment capabilities of the Launchpad, why do you need multiple SAP Fiori instances?

          • Hi John

            Perhaps I can expand a little on Brenton's question about multiple Fiori installations. I think the disconnect revolved around the definitions of "Fiori" (there's been plenty of discussion of what Fiori is and might be elsewhere on SCN in the past, as I'm sure people have seen).

            At its most specific, "Fiori" represents a particular set of apps that SAP have written and made available to purchase from their store.

            At its most general, "Fiori" represents a set of best practices, from UX/UI design, through to use of controls in specific SAPUI5 libraries (e.g. sap.m), the use of an OData service on the backend, and so on. A Fiori app can run inside our outside the Launchpad context.

            Taking the definition from the latter end of the scale, one can well imagine multiple "Fiori backends" that one might want to switch between with such an app - development, testing, QA, customer-written, specific point solutions, and so on. There is no "one Fiori to rule them all" 🙂

            So with this in mind, I wouldn't mind betting that a configurable backend URL option would be a welcome addition.



          • You're right, it is both. In this case, when I say SAP Fiori, I'm talking about Launchpad and the apps that run within it. That's what the SAP Fiori Client is designed to work with. That's why I said that if your app will run in the Launchpad, then it will be delivered to the SAP Fiori Client when you use it and it will run in the SAP Fiori Client.

            We have a configurable backend URL option - you configure the SAP Fiori Client application with the endpoint URL for your Fiori Launchpad. Is that different from what you are asking for?

          • Thanks John.

            To answer your question at the end - I don't think it is different, but only getting our hands on the juicy technical details and the app itself will clear things up ... so I and others are really looking forward to trying it out.



      • Hi John,

        I wanted to know touch points of this "Kapsel" based SAP Fiori Client with SMP 3.0, if any. I mean is there any way to link it up with SMP 3.0 Kapsel or that is a different architecture (UI5-Kapsel-SMP 3.0).


        Warm Regards


        • We have several customers who have built Kapsel applications that run SAP Fiori. We're working on enhancing SMP, Kapsel and the SAP Fiori Client to make this even easier.

  • Hi John

    I've few doubts. First of all I completely understand that we need to create UI5 screens for this Fiori Apps, can u let me know how we are using this MBO's with workflows. do we have any SDK for this like we do have for SUP & where are you going to register this App to Users. I'm curious to know about this..

    Cheers 😉


    • This isn't an SMP scenario, we're talking about SAP Fiori and a native client for accessing and avoiding the issues the mobile browser creates when it randomly purges its cache.

      I'm not a SAP Fiori developer, so I can't tell you how to create SAP Fiori apps, I'm sorry. I'm not aware of anyone who has done anything with SAP Fiori and MBOs or workflows. That's a different architecture.

  • Hi John,

    This looks extremely interesting and we are in the middle of implementing Fiori for internal use. I tried to look for the SAP Fiori Client, but wasn't able to find it anywhere. Do you know when it will be available?

  • Hi John, I heard from that great feature, too. But I didn't see it right now in the german Apple Store. Is it already available?

    Cheers, Sami

    • Hi John,

      the prerequisites say that the client can be used with demo data, but when launching the app we have to enter the URL of a Business Suite system.

      I really hope that some demo apps will be available.



        • I hope for a re-think of this decision. It's a shame not to let customers experience the latest innovations (Fiori in this case) through this straightforward channel.

          • Borut, as I've tried to describe here, the SAP Fiori Client is a runtime container for SAP Fiori that helps it overcome limitations of the mobile browser where the browser purges its cache periodically. It's not a tridional mobile application where there's local forms, views and so on. It is simply a way to run SAP Fiori without the performance issues that occur when the cache is purged. There is no local forms, views  and the application gets all of its data online from a SAP Fiori instance. Since the application's UI is provided by SAP Fiori, we can't implement a demo mode into the application, it's just not possible.

            This is an application for licensed SAP Fiori users, and you must point it to an instance of SAP Fiori in order for it to be able to do anything for you.

          • Hi John,

            I understand that the app is just a container with no local forms etc.

            I was thinking of providing a connection to a demo Business Suite system with some Fiori apps enabled, like Olivier CHRETIEN already pointed out.

            Thanks for the answer,


    • Hi John,

      Thanks for letting us know - I have two questions:

      1) Is there a iOS version coming as well - I'm struggling to find it in the app store (maybe i'm just not seeing it)?

      2) The android app seems to not like self signed certificates which I suppose is a fair security measure - however is it possible to bypass this check and proceed anyway? Personally my first attempt was to connect it to our sandbox system which is VPN only and has a self signed cert but it won't seem to connect and complains about the certificate being self signed.

      Looking forward to your response,


      • Hi Brenton,

        I had the same problem but managed to do a workaround by setting the fiori launchpage up to not switch to HTTPS in the SICF.

        Depending on whether you are on wave 1 or 2, the service that needs to be changed is

        Wave 1: /default_host/sap/bc/ui5_ui5/ui2/launchpange

        Wave 2: /default_host/sap/bc/ui5_ui5/ui2/ushell

      • The SAP Fiori Client is currently only available for Android. I will post here when the iOS version is available.

        You are correct, the application will not operate with self-signed certificates. As I understand it, this is a SAP product security requirement. An updated version of the documentation that describes this limitation will be posted online soon.

        • Hello,

          I just tested SAP Fiori Client on a Samsung Galaxy Tab3 tablet connected by wifi to my Fiori proof of concept testbed ECC6 server.

          I have a SAP Web Dispatcher terminating the SSL connection and using a certificate signed by our internal company PKI.

          The Fiori Client refused the connection until I imported the PKI CA certificates in Android security store.

          It means that for real productive usage a well known CA would be needed

          Then the launchpage display was sooooo long that I thought the application had crashed. In fact, looking at the http logs, it seems that Fiori Client downloads ALL available resources.

          The first access is therefore much longer than when using Chrome for exemple.

          Of course, the next displays are much faster with all apps resources cached.

          I have a bug with the Fiori Launch Page which is always blank until I press on the upper right "Gear symbol" icon. When using a standard browser the Launch Page displays ok.

          Concerning the lack of possible testing when not having one's own Fiori system, I really don't see why SAP could not provide a test URL from a server in the cloud with mockup data. If you want success for this application, that is the only way to go...

          Carry on the good work !


  • Hi John, Are there also plans of the fiori client for desktop..?

    what are the current platforms the fiori client is available for..? what does the future roadmap look like..?

    • No, no plans to support the desktop browser. We're just trying to address issues caused by the Mobile browser.

      The SAP Fiori Client is currently available for the Android platform. Support is planned for iOS as well.

      • That is what I already knew 🙂 ... I want to know when I can use it, because I just tested the Android App and it has many problems.... hoping the iOS App is better.

        • You can use it as soon as it is available on the Apple App store. I will let everyone know when it's available.

          What problems are you having? What's not working?

          • I just tried it on a Galaxy Note 3.

            So far I realized These Problems.

            - It does not recognize that it is a Smartphone and Shows tablet view instead.... this Looks like **** and cannot be used

            - attachments cannot be opened

          • Rendering content based on smartphone vs. tablet is not managed by the SAP Fiori Client - your Fiori application has to do that. This is not a problem with the SAP Fiori Client, so it's not likely that the iOS version will be any different.

            What kind of attachment are you trying to open?  We tested the application with a different attachment types. We receeived word recently that zip files and tel links weren't working correctly, so we're working on a fix for that.

          • The Standard SAP Fiori Apps, e.g. Leave Request is rendered correctly in android Standard browser on Galaxy Note 3, but rendered wrong in Fiori Client!

            The attachment is a PDF called in the following way. It does not do anything when clicking on the link.

            openAttach : function(value) {

                 var owin =, 'newwindow', 'width=400, height=600, scrollbars=yes, resizable=yes');


  • So, basically, this is Cordova + Kapsel plugins with the SAPUI5 files, right? As it looks like there is no magic involved, will SAP publish a doc explaining how to do your own Fiori Kapsel app for customers that use SAPUI5 / OpenUI5, but not Fiori? I guess everyone will benefit from that (maybe someone will than adjust the doc to make it work with Phonegap)

    What are the MDM (Afaria) capabilities of the Fiori client? As some configuration will be the same for users, I guess that with Afaria I can easily not only push the app out, but also pre-configure it (server url, etc), right?

    • Tobias, No, it is just a Cordova app. No Kapsel plugins today. The Fiori Client capabilities will be made into Kapsel plugins for a future release. When that happens, you will be able to make your own app like this using Kapsel.

      I don't understand what you mean about making it work with PhoneGap. As PhoneGap is just a distribution of Apache Cordova, what would need to happen to it for it to work with PhoneGap? It won't work with PhoneGap Build, but should have no trouble working with PhoneGap.

      If you read the post here (top of the page) you will find a description of everything it does today. There is currently no integration with Afaria, we simply tried to solve a performance problem created by the mobile browser and the way it manages its cache. Now that we have this released, we can start integrating more capabilities with SMP and Afaria.

      • Hi John,

        PG is a little bit more than just a distribution of Cordova (support and as mentioned by you: PG Build). Think of PG customers: they pay a support fee and Fior client is using Cordova. Would be nice for them to know how to make it run on PG. In case SAP explains what was done to solve the cache issue using Cordova, people can adjust this to PG.

        Good to hear that SAP is enhancing the product, but are there any infos available what to expect next? Like: in 3 month, Afaria integration should work, in 6 months ... ?

        • Tobias, like I said, PhoneGap is just a distribution of Cordova. There is nothing to let a customer know about how to make it work in PhoneGap as PhoneGap IS Cordova. PhoneGap is Cordova with a couple of additional things added on top of it. At the end of the day, it's still Cordova.

          • John,

            PG == Cordova + X. The X is what you pay for. Now, as Fiori client is using Cordova, it should not be a problem for a PG client to build it's own Fiori client. That why I asked for the documentation guidance from SAP. With that, every PG customer that is running Fiori (or SAPUI5/OpenUI5) should be capable of having it's own custom PG based Fiori client. WIth the PG support they pay for.

            In that case, the official app provided by SAP is the reference implementation, but everyone can do its own Fiori client app.

            Short: I am looking forward to seeing the documentation on how to do your own SAPUI5/Fiori client.

  • Thank you for sharing this. 🙂

    We are developing fiori applications using Wave1 architecture and we have applied our own CSS to the application.
    When we are testing the  apps on Fiori Client the said CSS is not reflecting for header and footers.
    Can you help in this? do we have to Theme Designer only for application header and footer CSS customization?


    • Rauf, The SAP Fiori Client was built to operate with server capabilities that became available with Wave 2 of SAP Fiori. You need to make sure your server infrastructure matches the requirements in the user guide (SAP Fiori Client – SAP Help Portal Page).

      We're simply rendering the app content in a Web View, so any CSS settings and so on should apply. I'm not quite sure why you're getting this behavior.

  • Hello John,

    i installed the fiori client from the apple app store on my Iphone 5 with IOS7.1 . it does not work. I get the Netweaver login screen with the message "You are calling this website with a browser that is not supported".

    --> is there a basis patch required so that the Netweaver accepts the Kapsel browser ?



  • Hi John,

    Great blog. In the beginning you said that Fiori client wiil work with SMP but does not require it. But is that for the future or can the current version available in AppStore and GooglePlay be used through SMP?

    Another question: Do you have any plans on releasing the Fiori client to Windows Phones?

    Best regards,


    • Right now, the SAP Fiori Client appliction doesn't work with SMP. With SMP 3 SP03 which was released last week (Ramp-up customers only, sorry), there is an updated proxy that supports Fiori access from a Kapsel application (the application would need to onboard with SMP and that's not supported with the Fiori Client today).

      The next release of the Fiori Client will have support for SMP and more. Next on my todo list is a blog post that talks about SMP and Fiori. You should find all of your questions answered there. Expect it next week.

      Yes, we plan on supporting Windows 8.1. Right now, Cordova on Windows 8.1 doesn't support some of the things Fiori Client does. We're working with the Fiori team, the Cordova dev team and Microsoft to work through all of those issues. No definitive timeline, but it is something we want to support.

    • There is no cached data in the Fiori Client. The application is running in online mode.

      Are you asking about cached web assets (HTML, CSS, JavaScript)? No, those are not cached today.

        • Sorry, typo in my previous response. Should have read: "No, those are not encrypted today"

          This has come up before and it's a tricky one. The SUP HWC encrypted web assets and essentially the app had to store them in encrypted form out of the way then decrypt them into the app's www folder when needed. It added a level of complexity and a serious performance problem.

          In the Fiori Client, we're not doing much of anything beyond simply allowing the app to keep its asset cache longer. To enable encryption of assets, we would have to do deeper modification of the container and perhaps make an extension to the Web View - something we're wary of doing as we're really trying to keep Cordova as out of the box (unmodified) as we can.

  • Hi John,

    Slightly left field question; is there the ability to get the source code to this to create a company branded (and potentially secured and preconfigured version of this client? If not, that would be a great idea, so that you can install through an enterprise app store a version that takes care of being slightly more secure.

    Also, it looks like according to the guide, if we have a requirement to authenticate against a portal that uses Basic Auth, this is not possible; so it would be good to understand specifically what authentication mechanisms are supported beyond "standard Fiori SSO" if you or someone you know can answer that question.

    e.g. My main concern is how you expose the Fiori server URL securely without creating a hole in your network.



  • Hi John,

    This is regarding running webdynpro applications on Ipad and Mobile, Netweaver 7.03 onwards we can run webdynpro applications on Safari, I tested this with safari and it is working but it is not working on Fiori client can we enhance our Fiori client app to handle this?

    I notice one more bug in the app,

    Missing "Done" feature when we use Fiori launch pad search to open a app which is Open in a new window..


    Gopi Sankuratri.

    • The SAP Fiori Client is designed to run the SAP Fiori Launchpad and apps that run within the Launchpad. We will not be supporting any other scenarios with the Fiori Client.

      Fiori Launchpad search is being managed by Fiori, not the Fiori Client. If you have issues, you should submit a support ticket with Fiori.

  • Hi John,

    I have the Launchpad working internal and external.

    It fails on SAP Fiori Client for iOS, with a  "The page cannot be found".

    I have checked the settings. The version is 1.0.6 but does not updated via Apples App store.

    I have enabled "Debugging" in the settings, but where would I look up any logs  to find out why the app is failing.



    • Have you tried looking in the documentation?  There's an option to enable logging within the application and you can view the log within the application as well.

      • Hi John,

        thanks, I have enabled logging and set log level to debug.

        When I open the application it just displays the "The page cannot be found" HTTP error message. There is a button "Home" which does not work, a picture frame which is not filled, and the Page adress.

        Where would I find the Logs then ?



        • The error message is telling you exactly what's wrong - the Fiori Client cannot access the remote site you've provided. That's it. Have you tried it in the mobile browser on the same device?

    • Hello John,

      my issue obove might be due to WLAN routing issues.

      Now I have a different issue when accessing Fiori Client from the Internet:

      Although the Fiori Launchpad is working fine in iOS8 Safari Browser (screenshot1),

      the Fiori client gives a certificate error:

      Certificate error.

      The page cannot be displayed due to a problem with ther server certificate.

      (see screenshot 2).

      Safari and SAP Fiori client use the same https://  link

      Screen1: Safari on iOS8 can handle the certificate.


      Screen2: Fiori Client Certificate ErrorFiori_client_cert_error_4sap.png


      Ulf Zeisberger

      • This is not a support forum, simply a post announcing the client. If you have support issues, you should submit a support ticket.

        That being said, a Cordova application (which is what the Fiori Client is), won't install the certificate for you like the browser will. Some of the certificate handling issues were fixed with the last release, but more options are coming in the next release.

        • Hello John,

          as you proposed, I have created a support ticket Mid December.

          Since Christmas and Holiday season are over now, I am looking forward to SAP taking a look at it.



  • Hi John,

    I'm just testing out the Fiori Client app now and the Launchpad definitely feels more responsive...

    One question if have - is it possible to launch the Fiori Client app from a URL? Allot of apps enable you to launch them via a url like: twitter:// or MyApp://.

    This would be very handy for when users receive emails.. They can then click on links in the email to open up the Fiori Client app. Being able to navigate to an individual Fiori app within the client would be even more awesome....

    • Jason, No - not today. It's something we want to enable, but there are some security concerns we will have to address first. You'd be amazed at the amount of security validation we have to do before we can release a product.

  • Hello,

    In the documentation of SAPUI5, sap.m library is supported in windows phone 8.1 as platform. However Fiori client support is declarad as below

    Browser Supported Version
    Internet Explorer Version 11 or higher
    Opera None
    SAP Fiori Client None
    Web View None

    Since, most of the Fiori applications use sap.m library, will the fiori apps will work in fiori client on windows phone or no?

    Kind Regards,