 <p>The problem is that the EditField will still try to use all of the width, which causes the VerticalFieldManager to also use the entire width available to it, effectively shoving off the password field.</p> <p>The only way I know of to do something like this would be to create classes that explicitly set their width to 50% of the screen. There are two ways of doing this: either create subclasses of EditField and PasswordEditField, or create a subclass of HorizontalFieldManager. The former option will be easier and more reliable across the different platforms, but will require two classes instead of one.</p> <p>To do this, you'll want to create a subclass of EditField and override its <code>layout</code> method to look something like:</p> <pre><code>protected void layout(int maxWidth, int maxHeight) { super.layout(maxWidth, maxHeight); this.setExtent(Display.getWidth()/2, this.getHeight()); } </code></pre> <p>Similarly for the PasswordEditField.</p> <p>Depending on how you want it to behave, you might have to override other methods as well. For instance, this code will (I'm pretty certain, haven't tested it specifically) cause any extra characters to be truncated if they dont fit in the desired area. If that's not what you want, you might have to override <code>paint</code> or change the layout based on the current text. Also, you should test it when tilting the storm screen to ensure the size updates correctly - it should work in most cases, but there is a bug that causes it to not update layouts/sizes if you have certain configurations of managers on the screen.</p> <p>If you decide to go the manager route (which, again, I don't especially recommend, as you'll probably run into many more issues), you'll want to extend either Manager or HorizontalFieldManager (might be easier to do the former, so you don't have to deal with some of the quirks of the HFM), and override its <code>sublayout</code> method. In this method, you'll want to call <code>layoutChild</code> and <code>setPositionChild</code> (in that order) for every field in the manager (in your case, the user field and the password field). Then, at the end, you'll want to call <code>setExtent</code>. I would refer you to the blackberry docs on this matter, but in all honesty you're better off searching for how to implement blackberry custom managers, or asking questions on SO.</p> <p>All that said, you might also want to reconsider why you want to do this. I can guarantee you from experience that there will be some phones where the UI does not look right - we tried a similar approach once, and eventually scrapped it because we couldn't get it to work from a UI standpoint on all devices. There are <a href="http://mobile-phone-digger.blogspot.com/2009/04/blackberry-phones-screen-resolution.html" rel="nofollow">lots of different resolutions</a> - some very narrow, some very wide - and if you go with this UI then some devices will have very cramped logins. IMHO, it would be preferable to be consistent with the other BlackBerry applications, and have username and password on different lines.</p>