Reminder App

by Agustin Vergottini » Thu, 03 Mar 2011 04:27:55 GMT


Sponsored Links
 Hello!
I've just completed a first version of what I want it to be an useful yet
simple to use Reminder application.

This first version allows reminders to be created, with a delay from 5
minutes to 24 hours. It's independant to the calendar.

What I would like to know is what you think and what features would be cool
to add.
I'm thinking group reminders, being able to select contacts in the contact
list to be reminded, either by email or sms?

Here's the link to the app, it's free!
https://market.android.com/details?id=com.pickle.reminder

Thanks!
Agustin.

-- 



Other Threads

1. How can I get the highest framerate with this quellcode?

Depending on UI event handling to produce smooth
and accurately timed  animations is usually bad idea

In your code,  if you remove delay you are just trashing
event pipeline, so UI will (and certainly does) become irresponsive.
And if you keep it in, your delays are unpredictable
(let me Guess, you are sending messages because you can not
affect UI from non UI thread? )

I recommend to look into LunarLander sample. Basic idea for smooth
animation is:
1. Use Surface to draw ( any SurfaceHolder subclass ), you can access
it from any thread
2.  You animation loop looks OK
3. I would recommend to create  something like finite automate / state
engine
to  provide smooth and controlled transition between game states

You drawing method would look like:
 redraw() {
        // field is prepared
        Canvas canvas = holder.lockCanvas();
        //  draw background
        canvas.drawBitmap(field, 0, 0, null);
...  draw whatever you like
// push it to the screen
     holder.unlockCanvasAndPost(canvas);
}

have fun

-- 

2. Service thread priority

I have two apps that use a service to upload and download files and
data. I've noticed that when the service gets very busy, it can cause
the UI to block, up to the point that Android shows a "force quit/
wait" popup. In order to avoid that, I run tasks in a service at a
lower priority. This way, the service will never cause the UI to
hickup. Also, the service stops if the app hasn't been used for a
certain number of minutes. I don't want to keep resources if the user
isn't using my app.

I have found that some of my users run apps that run services
permanently at normal priority. Such a service starts at phone switch
on, and keeps running indefinitely, downloading vast amounts of data.
My policy of being nice to other apps doesn't pay off: these agressive
third party services push my service away so it never gets anything
done. As one of my users told me, my app has hickups, until he kills
the service of this app X, after which my app runs smoothly, snappy,
and fast.

My question is, should I be nice to other apps and to the UI in my own
app, or should I just run a service and agressively take all resources
I need - or don't need? This is one issue where Android is different
from iPhone. We can run services, but by doing so, we can cause damage
to other peoples apps. Of course, my "question" doesn't require an
answer. I'm just curious after what other people think, what your
experience here is.

-- 

3. Cannot play audio on some phones

4. Booting Failure

5. Which IDE is better for kernel development?Is it possible in windows?

6. how do I load the new compiled kernel on my android dev phone 2 (htc)?

7. Is there any issues bugs or upgrade to Android kernal?