I think the ideas you are describing make sense, but the problem doesn't, at least to me. How will the user, having loaded the application on their desktop, now view the app on their mobile device, without also loading it there?
Is the use case that the user is actually a developer, and is resizing their desktop browser to be sized like a mobile app, and expecting it to behave as such?
Or somehow is the user "fooling" the app into thinking they are on one platform, and suddenly after page load it turns out they are on another?
That is, where is "step zero: detect what format the user is using to load the app" - perhaps, is this unreliable, and that could instead be the focus?
Also:what are the actual costs here to "reload" - why are multiple trips to the server required when a user, on the same device, needs to change from being on a mobile view to a desktop? If all users are subject to this ability to switch back and forth between views without changing devices (which obviously would require loading from the server), would it make more sense to include the layout differences in their initial load? How big are those differences expected to be, relative to the total cost of downloading the app?
I can see how an application could split to have a mobile vs desktop permutation, and have the desktop version potentially be 20%+ larger than the desktop version, but there will be a substantial amount of overlap between these - so rather than loading X bytes then X*1.2 bytes, could the application just be a single permutation for both, and only be slightly larger than the desktop build was to begin with? Almost certainly there must be significant overlap with business logic and likely also there is some overlap in view code too. Note that this is the roughly the same "question" as "either separate uibinder views or media query CSS" - I suggest that this is a totally separate discussion, after the initial problem and tradeoffs are better understood.
Once the initial JS is loaded, what are the other round trip calls to the server that are required? I presume this might include loading data from the server that cannot be cached? Avoiding extra round trips is the purpose of caching, and if avoiding latency and data usage is one of your key design goals, some special care should be taken to make caching as effective as possible.
On Sunday, March 30, 2025 at 6:34:37 AM UTC-5 kumardiv...@gmail.com wrote:
This is the problem I faced for a GWT application. I need the best approach to solve this:
The challenge is that the current design approach requires a complete page refresh when switching between UI layouts (for example, from a desktop view to a mobile view). This process means multiple server trips, which can be slow and use extra data—especially on mobile devices.
On Sun, Mar 30, 2025, 16:52 divyanshu kumar <kumardiv...@gmail.com> wrote:I only want the best approach on how can we implement this feature...Currently the issue is when user change the interface from mobile layout to desktop it will took multiple visit to sever which will be expensive...On Fri, Mar 28, 2025, 23:25 Neil Aggarwal <ne...@propfinancing.com> wrote:This may be a big change, but why not make it a browser-based app? Then desktop, mobile, etc. are all able to use it without needing to download and install anything.--On Thursday, March 20, 2025 at 4:38:21 AM UTC-5 divyanshu kumar wrote:I'm working on a GWT application that was originally designed for desktop screens, but I now need to create a mobile-friendly layout that retains the existing functionality. As I'm relatively new to GWT and UiBinder, I'm looking for guidance on the best practices for adapting my UI for mobile devices.My specific questions are:
- Responsive Design: What strategies or design patterns can I use within GWT to implement a responsive or adaptive layout?
- UiBinder Tips: Are there any particular tips or resources for effectively using UiBinder when designing for mobile?
- Code Reusability: How can I maintain the same functionality across both desktop and mobile versions without duplicating too much code?
Any sample code recommended libraries or links to useful tutorials would be greatly appreciated. Thanks in advance for your help!
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/76a45ad6-48e2-4a88-8966-c5d0ba985ac2n%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/ed7900c8-5392-40c8-8e31-cca7c8a14222n%40googlegroups.com.
No comments:
Post a Comment