iMe 2.0.1 delayed
26/11/09 20:45
A bug has been spotted in iMe in the images section, when adding images.
I submitted the reqorked images section to Apple, only to find out later that iMe crashes on iPod touch. I didn't find any ipod touch to test the application until today morning, so the application will be delayed a bit.
I submitted the reqorked images section to Apple, only to find out later that iMe crashes on iPod touch. I didn't find any ipod touch to test the application until today morning, so the application will be delayed a bit.
iMe Version 2.0
30/10/09 16:15 Filed in: Releases
And the beta became a final...
iMe v 2.0 was released yesterday. And implements many new features and facitlities, important and powerful. Changes to iMe include thumbnails for images, .txt file support, many big fixes, performance fixes, voice recording, voice memos, and many more. Read More...
iMe v 2.0 was released yesterday. And implements many new features and facitlities, important and powerful. Changes to iMe include thumbnails for images, .txt file support, many big fixes, performance fixes, voice recording, voice memos, and many more. Read More...
iMe beta was submitted Yesterday!
02/10/09 02:25
iMe was submitted yesterday at Apple! A list of some new features can be seen here!
iMe feedback
07/09/09 01:58
Well, iMe feedback is really positive, but I have also received some criticism about how things work in iMe. So, the next version of iMe is currently in beta, and you should probably check out the list of bug fixes scheduled in the next version. Read More...
iMe was released today!
30/08/09 21:21 Filed in: Releases
iMe submitted to the app store today!
06/08/09 16:09 Filed in: News
Well, iMe is submitted to the app store today.
After development, and many mishaps, iMe is finally submitted and waiting approval. However, what you see is a very stripped down version of the original iMe that contains AES-256 encryption.
Unfortunately, iMe’s story is a long one. Longer than what you might intend to read. It has been rewritten 2 times, because of bugs in the CoreData system by Apple. However, its functionality has been expanded a great deal since the version with AES encryption.
Why that encryption has never made it in the final version? Well, that’s because of bureaucracy. In order to release an application with any kind of encryption that is larger than 64 bit, you must have a special license, specific to your application, that takes about 45 days to obtain. Imagine my surprise when I saw (after the program’s completion) that I should wait another 45 days, let alone the long review process by Apple.
So I decided to release iMe without that encryption, hoping to implement it in a later version, after I have obtained my License for using encryption. That doesn’t mean that iMe is not safe. It just means that it would be a lot safer using encryption.
After development, and many mishaps, iMe is finally submitted and waiting approval. However, what you see is a very stripped down version of the original iMe that contains AES-256 encryption.
Unfortunately, iMe’s story is a long one. Longer than what you might intend to read. It has been rewritten 2 times, because of bugs in the CoreData system by Apple. However, its functionality has been expanded a great deal since the version with AES encryption.
Why that encryption has never made it in the final version? Well, that’s because of bureaucracy. In order to release an application with any kind of encryption that is larger than 64 bit, you must have a special license, specific to your application, that takes about 45 days to obtain. Imagine my surprise when I saw (after the program’s completion) that I should wait another 45 days, let alone the long review process by Apple.
So I decided to release iMe without that encryption, hoping to implement it in a later version, after I have obtained my License for using encryption. That doesn’t mean that iMe is not safe. It just means that it would be a lot safer using encryption.