I have noticed that as well so you're not alone.
What should be the exact reason for the same ?
I beleive this was mentioned in a session at the developer conference. iOS devices typically have less resources and rendering blur can be expensive in terms of processing power, so some of those effects aren't drawn.
I honestly don't know. Right now I'm only using the blur sparingly so I just shrug-it-off and haven't even tried to find the cause. I suspect that the iPad and iPhone just don't render the blur effect like Windows machines do; similar to the way that different browsers render objects differently.
Or maybe it's a bug.
Either way, knowing that the blur effect renders differently depending on platform is going to keep me from using it extensively.
I didn't attend the conference but recordings from a couple of the sessions were released and in one of them I recall the blur effect and gradients as being identified as having high overhead but I don't recall any mention of it being suppressed on the iOS devices for that reason. Perhaps somebody from FMI can confirm or deny this?
I, too, clearly remember it being explicitly mentioned in Andrew Paulsen's session, and took notes to that effect.
He started by stating that "as the blur setting goes up, so does the cost" (even on desktop), then went on to mention the point you remember, that they skip blur alltogehter in Go for just that reason. There was an exception, however: I believe popover drop shadows do draw the blur effect in FM Go (although I didn't explicitly make a note of that). I'm looking right now at a Go solution on my iPad and can see the blur effect in a popover drop shadow.
I remember reading somewhere that the Inner Shadow will not be rendered in th iOS environment due to performance issues.
FYI this is mentioned in the FileMaker Go 13 Development Guide in Chapter 3 - you can't "display shadows on layout objects".
FileMaker 13 Certified Developer
- - - - - - - - - - - - - - - - -
Phone: +61 2 9484 6565
Mobile: +61 418 468 103