martino2k6 / andneko Goto Github PK

If anchoring, for example, to a view located in the top left corner of the screen the screenmate will position above the view and thus attempting to go off-screen.

The implementation should figure out whether there is enough space available for positioning, and if not it should pick an alternative strategy (ie below, falling back to centre for views taking up the entire screen).

The user should be able to manage a list of apps in which the screenmate should not be drawn.

Android doesn't push this information, so there would need to be a Service to poll for this information from the ActivityManager. Is there a more efficient way?

The user should be able to manage a list of apps for which the screenmate should not act on accessibility events.

Would be nice if the fill/background could be set for the screenmate. Perhaps allowing a solid colour, gradient, or even a picture (makes sense for such a small size?).

Doesn't seem to happen on a local build. Figure out what the error is, fix it, and remove the build script workaround.

Modes could be any of TL, T, TR, R, BR, B, BL, L (for top, left, right, bottom).

It may not always be possible to position the screenmate in such a way that it never gets in the user's way, obscuring some important information. As such the user should be able to long-tap on it, get a visual cue that dragging has been activated, and move it.

How long should it stay fixed at the selected position though? When can we be safe that we will no longer obscure the UI with the next move?

It would be a nicer UX if on first opening the user was guided through a list of swipe-able instructions and a little tutorial on how the app works. For example:

1. A little detail on Neko's history and how it works on Android
2. Prompt to enable Aneko from the Accessibility Settings
3. Request the user to click on a couple of views to make the screenmate move
4. ???
5. PROFIT!!!

If the user quits from the tutorial then it should persist state. The tutorial should show the current and total page indicator. It should also be possible to skip it and head straight to the app.