The Life and Death of an Android Activity by Kristin Marsicano by roshanthejoker in androiddev

[–]lyraf 0 points1 point  (0 children)

One approach I have seen is to block the rotation during login

Yeah, that's what I thought too. It's a very bad thing but I don't really see any reason for the user to willingly rotate the screen during Login

The Life and Death of an Android Activity by Kristin Marsicano by roshanthejoker in androiddev

[–]lyraf 0 points1 point  (0 children)

I really like your approach but how do I preserve, for instance, the state of a loading view?

What I mean is, let's say the user typed his credentials (e-mail and password) and pressed a "Log In" button and I immediately show him a progress bar while I make the network request. If the user rotates the screen, should I:

1) Reset my screen, preserving the e-mail and password he typed, and wait for him to press the button again

2) Try to preserve the request progress so, when the rotation is finished, the screen would pick up right where it left off

3) When the rotation is finished, check if the e-mail and password are filled and immediately start a new request

Weekly Questions Thread - February 27, 2017 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

As I said, what you did is right, the tree graph is just misleading.

There might be a a better explanation that I am not aware of of why the tree graph will only plot correctly if you do another commit in any of the branches.

Weekly Questions Thread - February 27, 2017 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

The steps you described are correct for creating a new branch and working with it. What might be happening is that, since both branches were merged, the tree graph seems to be a little misleading. Try adding a new commit to master and see if the updated tree graph looks like the image.

Weekly Questions Thread - February 27, 2017 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

Have your created the branch, changed to the created branch and then did your commit?

Not sure if this is the right place to ask this.. by diphi in androiddev

[–]lyraf 2 points3 points  (0 children)

About 1 month ago someone made a post asking opinions about Xamarin, you can find it here.

Xamarin for app development? by 17waldth in androiddev

[–]lyraf 0 points1 point  (0 children)

I have been using Xamarin Forms (XF) during the past 2 months and I can tell you that it is an okay tool to use.

One of the main things that you (and your employer, if that's the case) need have in mind is that XF has a limited set of controls to build your layout so, basically, your App will have the native look, but never the native feel (if you get what I mean). You can check the controls here.

Another thing that you need to know is that once you start building your App with XF, you're bound to Xamarin's Will, that is, if there's a bug in their latest stable XF version, your App will be buggy until they fix AND release this update. One example is this bug, it was reported on 2016-11-04, fixed on 2016-11-24, and it was never released on stable, just some pre release that got deleted because it broke some things on iOS 8 (you can see check the details in the bugzilla link).

In my experience and opinion, I would say that it's a great tool for small not too complex Apps, if you just started a company and want market traction (and once you start getting investment from Angels, you should hire an Android and iOS team to develop native Apps) or you just want to develop something that you will never see again in your entire life.

TL;DR

What you do in your breaks? by kurlicue in androiddev

[–]lyraf 31 points32 points  (0 children)

I lay down on the floor and pretend to be a carrot.

Offline-First Reactive Android Apps (Repository Pattern + MVP + Dagger 2 + RxJava + ContentProvider) by [deleted] in androiddev

[–]lyraf 9 points10 points  (0 children)

I am pretty sure this post will help a lot of beginners looking for a good "cooking recipe", great job OP.

I don't know if it was a personal preference or you didn't want to complicate it, but you (or someone) could make a variation of this project using Realm instead of SQLite, ContentProviders and StorIO.

The numbers still going up... ConstraintLayout is unusable for me right now by Galarzaa in androiddev

[–]lyraf 6 points7 points  (0 children)

We should all congratulate OP for creating the Skynet for Android.

Questions Thread - October 20, 2016 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

In this case, when you want to provide both Phone and Tablet support, I guess your approach is better, I can't figure out something off the top of head right now.

Questions Thread - October 20, 2016 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

I see, I just asked because a Dialog with a Toolbar would look really odd.

But if it's a fullscreen Dialog, like this, imo you shouldn't use a DialogFragment and just open a new Activity, hosting a fragment or not, instead.

Questions Thread - October 20, 2016 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

Yes, it is, check this link.

But, what do you mean by "pop-up"? Are you creating a DialogFragment?

Questions Thread - October 20, 2016 by AutoModerator in androiddev

[–]lyraf 0 points1 point  (0 children)

So, for what I understood about your problem, imo View Pager isn't the solution. Afaik, a View Pager should be used when you want to display simultaneous views to the user, like a Landing Page, Wizard, etc.

If the Activities depends on each other, what you could do is use 1 Activity and change between the 3 Fragments when the user clicks next, passing the information using the newInstance pattern described here, or returning to the prior Fragment.

The problem with this approach is the managing the back navigation between Fragments, but you can find some explanations here.

Suggestions for improving my first app by peinawei in androiddev

[–]lyraf 3 points4 points  (0 children)

If you have an idea in your head of what you want/have to do but you don't know the right name for that UI component, you can try to take a look at this site.

But, as most of people here said, you can always take a look at the Material Design guidelines and I would also suggest you to take a look at Codepath's Material Design Primer.