Is it possible to create iPhone like cover flow in J2ME (specially Nokia)?
If yes, what could be the logic to create it?
J2ME Polish can be configured to provide lists in a cover-flow like UI (see here).
You might also be able to persuade LWUIT to produce something like coverflow, but I have less experience there.
Related
My understanding is that the new Hub control is supposed to replace the Panorama control in Windows Phone 8.1. However, the new Hub control does not have an ItemsSource property like the Panorama control did. I can still use the Pivot control, which supports the ItemsSource property, but its only available in my phone project. I would like to use the Hub control because it is available in both the Phone and Store projects.
Is it possible to extend the Hub control somehow so that it supports any given number of HubSections, depending on how many section items are provided to it via the ItemsSource collection?
I think I understand what you want to do is something like Hub.ItemsSource to create the different HubSection for you? This is dramatically against the recommendations of the control team. There are several reasons. The first is the intent of the control to be a curated list of items meant for the Hub page of your app. The second has to do with performance.
Having said that, there is nothing to stop you from creating an Attached Property that implements the same concept you are wanting. But dynamic HubSection are simply not how the control is intended. You might want to comment back saying "Then how is it supposed to replace the Panorama control?" The reality is, the Hub control is the closest thing we have to a Panorama control, not a one-for-one replacement.
I bet, for sure, you can live without it. But you certainly are not the first to ask. Developers want everything to be as dynamic as possible. But that isn't actually best for performance. And, performance is worth a second consideration here. I think, like you, a lot of developers are going to be rewiring as they start to build universal apps instead of Silverlight apps. I'm sorry it's not one for one.
Try this solution from Diederik Krols - http://blogs.u2u.be/diederik/post/2014/01/05/Using-the-Windows-81-Hub-as-an-ItemsControl.aspx
I have a project which requires the development of a mobile site which works on both smart phone and tablet devices. I have read much about mobile design, concepts of "mobile first", responsive design, etc. One thing I have not seen covered is discussions on work flow, particularly at the layout design phase.
What I am not sure about is whether I should focus on the wireframe model for the phone site layout first, and then work on the tablet layout once the phone layout is finished? Or is it better to work on developing both phone and tablet wireframes concurrently? Which method is less problematic in the long run?
It really depends on how many of these you've done before as well as your designer.
Some designers need to work on the desktop first and bring everything down from there, it's just what allows them to be be more creative.
Having said that you're better off looking at going mobile first. I've seen a lot of responsive projects run into issues around linearising the large desktop content areas down into a tablet and mobile layout while still maintaining brand recognition and a synergy between the designs (yeah, I used 'synergy').
It helps if you're able to get your hands on REAL content for the site so you know exactly what you're dealing with. Use a framework like Bootstrap or Foundation to rapidly prototype some ideas with the real content and test to see what does and doesn't work.
When it comes to designing, try and design things in modules. Check out Style Tiles for hints on how to design with that workflow.
Best advice is do what works for your team, you will make mistakes anyway so even if you ignore everything I've said keep it in the back of your mind. Use real content, prototype/test early and don't be afraid to go through a few iterations.
Oh and finally, if you do go Desktop first design, display: none; is not a suitable solution for your content problems later on.
How can I communicate in a very simple and effective way the path the user takes through my application?
I'm currently working in a Ruby and Rails environment, so I tend to visualize my application in terms of RESTful URIs. So for example, if I want my users to sign up, I could match a new route called /users/new. The thing is, I would like to see beyond that specific action, and visualize how many pages or forms does it take to create an account and some business logic associated with the process in general. In other words, I'd like to see a mix of a workflow diagram and some implementation details (at an interface level).
I was thinking in showing mockup pictures wrapped in boxes, and relate them through arrows with their corresponding GET, POST, PUT, DELETE methods and URIs attached to them. I think it is a good idea, but I haven't seen examples yet that inspire me.
In your experience, what helps you see the big picture? Balsamiq mockups allow to define links and navigate through the app, but it doesn't help to conceptualize.
Have you thought of using a mind-map? You could try the free FreeMind
If you stick with UML, you could consider an Activity diagram.
I think you're on the right path. Showing different screens with possible combinations of users' transactions between them is a good technique. Basically you would be able to show user's flow through your application and stress out decisions a user will make on the way.
The good example for it was presented here http://vimeo.com/43869717
This technique called Storyboarding. You should be able to find some examples. But the one I mentioned above is one of the best Storyboarding techniques. I use it all the time to show the big picture and present application workflow from user perspective to my team.
I would like a list of advantages/disadvantages of J2ME, mainly MIDP. I figured that this would be the best place to ask since there seems to be a wealth of knowledge in this forum.
Currently I have the following advantages in J2ME.,
* Rich Clients
* Offline use
* Consistency of applications across platforms
* Reuse of existing code base
I don't really have a list of disadvantages although I am sure that there are plenty. Any views on either advantages/disadvantages[ie., Limitations of J2ME] would be welcome.
Thanks in advance,
Tilsan the Fighter..
Noone of them. Main disadvantage is paranoidal security model. For instance read here.
We cannot able to access the database directly.For database we should connect to intermediate.From that intermediate we should access the database.From that intermediate the result is return the j2me.Here the intermediate is any one of the following such as servlet,etc.
As barmaley said and the link given. LWUIT allows you to create really nice J2ME apps, but really, J2ME is in it's death throws. Unless you have a specific requirement to use J2ME now, you'd be better off targeting Android.
Is there a way to determine what kind of data plan a device has so an app provides a less rich experience if a data plan is not available? I imagine the connector factory would still be able to return me an HTTPConnection but it would cost the user serious money for lots of data, and I'd like to be nice and prevent that.
I thought there would be a way to query device capabilities in the MIDP API, but maybe it's in CLDC?
Since you mention it in your comments, you can probably make a Symbian OS C++ application that only connects via a specific set Wi-Fi access points (and just stay offline if none of these are available) but I can't think of a way to figure out the current user data plan or whether a given Wi-fi network is free.None of that is available in J2ME, at least not until something like JSR 307 is implemented.
You might want to look into how the Nokia IAPInfo API behaves on actual phones (including Sony-Ericsson and Samsung Series60 phones, potentially) since it is the closest thing to what you want.
No there is no way to do this.
As far as I know there is no way to do this. To address this precise issue, on first download we provide a big bold letter warning saying our apps require data plan. You can do something similar.
Or you can provide an option on first download for the user to say whether he has a data plan or not, and provide a degraded user experience if he doesnt. Dont forget to keep this as an option in application settings and allow the user to enable data services later, as he/she may get a data plan and want to use your app.