A Tweak

Let me come through with a little pull, I’d toiled around with the previous story.

Let’s revisit the last blog in a jiffy,

The First Screen

Why update?

A first look can convey a mental visual of what I desire.

Ins and Outs of an android app

But, with the technical aspect counting for a furnished app, I can’t afford to gamble on user-experience. This story is around a small fix that I’d to tussle to get the app running seamless.

Where update?

This update is unfortunately on the UI. There’s no better place to impress users or scope for a revision than the Interface.

Data modeling and APIs are well-defined for the 1st screen and infact, don’t play the complex bit here (Comeon, its just a user table with insert and update). I came upon this hassle while I’m busy amidst the 2nd screen, Home Page. I specifically wanted to pin this up so that, I explicitly fulfill my deliverable targets (self-satisfaction, thats all :D )

What update?

There was a ‘gear-jam’ that I’d to make with the Edit Profile Action bar. For the first time a user logs in, the Action title is plain & simple. But, as the user visits the page again, the HomeUpNavigation is enabled to take him back home.

A simple gnarled Action bar with no colleague controls shown up at the time of registration.

An advanced peer-to-peer toolbar that’s got an amazing connectivity, shown up only after the reg.

The flaw in the plan was around this — there was no instance of the parent activity when the up button was shown, so upon click, it shut my app down.

This keeps popping everytime you flush a stack or load the homepage. Annoying right?

The home screen gets reloaded everytime I navigate in or pop a page off the activity stack. I set a singleTop launchMode to check on this. Easy solution, right. It also solved me the trouble of developing a swipe left transition when popping a page off the stack.

Here’s one who opens his thoughts for others to cognize.

Not everybody is comfortable with sharing a personal description.

I faced some challenges with parsing the user data into readable text — omitting blank data and rendering a formatted ready-to-read version of the available data fields.

I’d to tell you this with this post, coz, this is an exclusive UI update tracker, & probably the upcomings needn’t graze this side of my android development.

End Note

I didn’t want to sneak into the begone stories and alter content. I want to put up anything new into a story so that I comprehend for myself why I’d to make these changes & what was my thinking strategy when I designed the page in debut. That little conscience can help evolve a developer to a DESIGNER. That’s my stake for the day.

That said, Every update deserves a PLOT.

So long for the next story :)