Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HowTo on first launch of AIMSICD #181

Open
SecUpwN opened this issue Nov 19, 2014 · 11 comments
Open

HowTo on first launch of AIMSICD #181

SecUpwN opened this issue Nov 19, 2014 · 11 comments

Comments

@SecUpwN
Copy link
Member

SecUpwN commented Nov 19, 2014

Hi there, everyone! I've been receiving some valuable feedback of a kind friend of mine. Asking around, several other people confirmed that it would help the average user a lot to have a small "HowTo" guide when starting our App the first time. A nice reference App I instantly had to think of was the funky PimpMyRom by @Androguide. His HowTo is quick, intuitive and self-explanatory. What do you think?

  • UPDATE: Our current DISLAIMER shall be added to this "HowTo" to make people fully read and accept it. We also think that it is important to add a red-colored notice that our app is still in ALPHA stage and that the phone should be left at home at all times when participating at demonstrations!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@E3V3A
Copy link
Contributor

E3V3A commented Nov 20, 2014

Yes, I'm on it. Once I'm done with the content you guys we'll have to put it to shape for including it in the app. Talking of which.

Q: Is it not preferred to include app help "text" as a text file to be imported by app?

@SecUpwN
Copy link
Member Author

SecUpwN commented Nov 20, 2014

Q: Is it not preferred to include app help "text" as a text file to be imported by app?

Good mornIng! Are you actually talking about #174? Thought those are two different things. This Issue is meant to implement a quickstart guide, which only appears on startup once to make the user aware of the most important functions of our App. Below, you see what PMR is doing using this blue hand. Install the App and launch it to get a feeling for what I mean exactly. What do you think of this, @He3556?

PimpMyRom

@E3V3A
Copy link
Contributor

E3V3A commented Nov 20, 2014

Ah ok, got it. But the question remain. Where do you most conveniently put the text? Seem a bit dumb to have to edit XML files, when there is only some text blob needed.

@SecUpwN
Copy link
Member Author

SecUpwN commented Nov 21, 2014

Where do you most conveniently put the text?

Maybe @Androguide finds a second to reply on this one?

@Androguide
Copy link

For the quick start guide in my app I used this library: https://github.com/amlcurran/ShowcaseView

It's pretty straight forward to setup and it's nice looking. You can showcase any UI element, including navbar buttons.

SecUpwN added a commit that referenced this issue Nov 25, 2014
@SecUpwN
Copy link
Member Author

SecUpwN commented Nov 25, 2014

Awesome, thank you so much for pointing me in the right direction, @Androguide! I have just implemented SCV as a dependency directly into our build.gradle and hope that my team as well as @tobykurien will help me on adding the further usage. @E3V3A, are there specific parts of our App you'd say should definitely be showcased on start-up to make them more clear to the average user?

@He3556
Copy link
Collaborator

He3556 commented Jan 19, 2015

REMINDER for the installation & setup wizard (for the first start of the app)
We need to wait until the db is downloaded before we check the CID against the data of OpenCellID. Otherwise we get a wrong alert just right after the installation.

Maybe we use a flag, that is changed when the db download is finished?
But only the CID check needs to get stopped not the changing LAC detection.

@SecUpwN
Copy link
Member Author

SecUpwN commented Mar 4, 2015

@He3556, we could also replace ShowcaseView with WizarDroid or even WizardPager.

@SecUpwN
Copy link
Member Author

SecUpwN commented Jul 29, 2015

@DJaeger agrees on adding our current DISCLAIMER to this HowTo since nobody seems to read it. I have updated the OP with some further thoughts. Everything that shall be done will be added there.

@SecUpwN
Copy link
Member Author

SecUpwN commented Dec 9, 2015

Just tossing it in: I smiled when using Omni-Notes, it features a great AppIntro. Furthermore I'd like to know if it makes sense pulling our CHANGELOG directly into the app to show it with ChangeLog Library?

@SecUpwN
Copy link
Member Author

SecUpwN commented Mar 3, 2016

Some inspiration from the SMSSecure Issues list for participating developers: http://emptystat.es/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants