Hello XDA'lers,
I'm proud to present you my latest app, called OpenOffice Document Reader.
Boring part about its history following... Feel free to skip it if you are lazy like me
I've already released it a few months ago out of frustration that there's NO native OpenOffice (LibreOffice) viewer for Android out there. However, first versions contained a lot of bugs, were slow and simply... bad.
Then, I started working together with my colleague Andi and rapidly improved the app a lot (from 3 to 4 stars average rating in Android Market) and seeked some interest from an Australian wine company, the official OpenOffice.org project and others.
However, let's go on with the interesting stuff...
OpenOffice Document Reader, Android's first native OpenDocument viewer, features most of the things you'll demand from a viewer, including zoom, copying, text search and other little gadgets almost none of you will ever use.
Originally it was meant to integrate seamlessly into the Android system (no icon in the launcher, no built-in file chooser), but since I mostly respect my user's opinion I've added both of the features I never planned to add (namely an icon in the launcher and a built-in file chooser - contributed by David).
Otherwise you're still able to open your documents using other apps, like GMail, Dropbox, Box.net, the official stock Android browser and others... (please keep reporting me what apps you're using to open your documents!)
That's it. I can't wait to read how you like it.
If you didn't already download it while reading this: Download at Android Market!
Maybe one thing I should add: Yes, we're working on editting. Hopefully Andi, TomTom and I can get it working soon for you.
Have a nice and open-sourcy day
Tom
PS: Yes, this is - and will be for ever - free open-source software released under GPL or something like that. Feel free to fetch the code at GitHub and don't forget to take a look at the underlying library called JOpenDocument by Andi.
PPS: Sorry for the awful amount of hyperlinks, but they tell you more than thousands of words.
Related
Hi,
this is my first Android App, so please bear with me if there are still errors. It was a major task to start Android programming with such a tough idea, but well, I did not say I started programming with this app
DroidReader is a PDF Reader Application. It uses native code in the background, to be specific, it uses the MuPDF rendering software/library. I'm aware of existing closed source PDF readers and some approaches to do it all in Java. So this should be different as for now.
DroidReader is Free and Open Source Software (licence is GPL v3).
The App and its sources are available at Google Code:
http : // code.google.com / p / droidreader
The App is now (since v0.3) also available via SlideME.
(I'm sorry, I can't post a full link as of now, as I'm still a "new user" on this forum, despite reading it since years... so please remove the spaces for now, I think I'll get that settled soon.)
Note for users: This application needs a file manager in order to open PDF files. Generally, you should be able to use a file manager of your choice and just click on the PDF. If you want to use the "Open" menu item, then a filemanager that understands the openintent.org's PICK_FILE intent is needed, e.g. the OI File Manager.
This App needs at minimum the Android 1.5 platform.
Changelog:
v0.5: rewiring of code, noticeable to end user: smaller install footprint, better cmap handling, small changes & bug fixes
v0.4: support for automatic tilesize calculation, now it should work on bigger screens, too. Also there is now a configuration dialog that allows to specify the default zoom level.
v0.3: added an "about" dialog
v0.2: lots of improvements, UI slightly modified for easier navigation, zoom&rotation fully implemented, ability to open password-protected PDFs, CJK support, lots of bugfixes
v0.1: initial version, still very rough and not all that shiny and thus not yet in the Market. Download available on the project's homepage.
Please note that any comments are very welcome! You can comment in this thread (and I will try to answer any questions ASAP) or on the mailing list (see the project's home page).
Similar approach in another project
Hi again, I just became aware of a similar project (well, as I said: I did this to learn Android programming as well, so this doesn't mean my time was wasted). I hope that we can combine our efforts soon. It is also at Google Code (and I still cannot post Links) and it is called "Android PDF Viewer", and has a short Acronym which appears as project name in URLs: APV. It also uses the MuPDF library and is also GPLv3. Just for your information.
To have an android PDF reader with the capability to make annotation and highlights is the most important thing. Apple has that software called "iannotate" and it manages it perfect. Android should have one. Is ther any expert working on this?
Best reader for Pandigital Novel
DroidReader is the best PDF reader I've found for use on the Pandigital Novel (hacked). All the others require one to drag your finger to move from page to page. That isn't as handy as the next and previous buttons. Adobe's reader is useless because it doesn't let you jump to a page.
I wish you'd enhance DroidReader to remember the last page in a PDF. I've also found some pdfs it won't open, but Android PDF Viewer will. The problem with Android PDF Viewer is that it is SLOW (unless I'm using a different one than you are referring to). It is so slow that it is unusable on the Novel.
Thank you for the feedback. I think I can manage to finally hack a bit further on this and your suggestion is certainly among the easier things still in the pipeline. I got a bit distracted recently, but I'm still motivated to further improve Droidreader. Being distracted, I am also not very up-to-date as to what's the fastest PDF reader available... I think in about two weeks, some development efforts should been done... I'll update this thread then!
I bought a copy of Andricious some time ago and I adore it. My entire
life is structured around my del.icio.us bookmarks, and having such easy
and well organized access on my phone has been wonderful. I can't tell you how many times I have looked at an app on the market and thought, "Why do I need this? The same information is two clicks away via andricious."
However, as you have probably heard (the screams of despair), delicious iѕ being shut down by yahoo.
There are a few projects out there which are compatible with the delicious v1 api. The most popular that I know of is pinboard.in. Scuttle and del.irio.us/rubric are open source variants, though they aren't as actively developed now as they once were.
Would it be at all possible to make the api url in any of the android del.icio.us apps a configuration option, so that users migrating to compatible services can still make use of the del.icio.us apps currently available?
I just published a port of my Delicious app for pinboard in the market.
XDA Thread
Project Site
I have been consistently wanting a viable video editor / movie maker for android, and finally there's some hope.
- Background: My work phones have been iPhones for several years, and I own a personal iPad 2. Currently iOS is in a different league, above Android, when it comes to video editors / movie makers (yeah, I said it...). There is nothing comparable to Apple's iMovie on Android (nothing that is multi-platform, that is). I know there have been apps by individual vendors (Samsung etc.) that only work on their hardware, and even then, there were buggy (I have the Samsung app, and it has a lot of issues).
So, the good news is, I Just came across this tonight - http://blog.wevideo.com/bid/272187/W...pp-for-Android
It's a new app called WeVideo (just released, so it's still in BETA), and it's pitching itself as an iMovie-like editor for Android, with some cloud-based features and other differences, but what's important as it appears to provide full "movie making" capabilities across various Android devices.
I just tried it out and it works well, with a few oversights like:
- No transition control
- No volume control for music tracks
- No local storage of published video (not that I've found anyhow)- This is its biggest drawback IMO
But with the app being brand new and in beta (AND FREE) I'm hopeful that community feedback will sees this things are addressed.
So for now, if you don't mind using their simple theme, and don't want to include your own music, it works pretty well.
It's also nice that it supports publishing of your videos directly to YouTube, despite not exporting to sdcard etc.
not supported on my device
c3n_dhol said:
not supported on my device
Click to expand...
Click to collapse
Be patient. It was literally just released. Their website states that additional device support is under development.
Developers have to know that there is huge demand for a working movie-making app for android. I'm really hoping that this one pans out. I know many people who would be willing to pay a decent fee for such an app.
Works for my i717.
:beer:"We can't stop here! This is Bat Country":beer:
Downloading feedback later
Sent from Qarth
Looks very promising.
Sent from the Mars Rover.
This is a long shot, but I since the demise of Google Reader (which this app supported) the developer has decided to no longer continue the development of this app. A tragedy; I think we as a community should try and sway him to continue it instead, adding new back ends, both Feedly and TOR (TheOldReader) support would be great. I would love to continue using this app, as it is probably the best RSS reader I have encountered on Android. It is my hope that we can either convince him to continue the project or allow someone else to (any volunteers ?).
Flow Reader gives you an easy way to be on par with your RSS/Google Reader feeds on the go. It was built to provide a minimalist and seamless experience for offline browsing, while delivering additional features not found in similar apps.
Some of the main features include:
- A sleek and fast user interface;
- Offline item content and state caching;
- Multiple simultaneous downloads for fast content synchronization;
- Content filters that automatically mark as read the items you're not interested in;
- Sort items by state (latest/unread/starred) or author;
- Smart algorithms that remove ads and other undesirable content from items;
- No ads.
Click to expand...
Click to collapse
The Developer posted this statement in the most recent app update:
As you sure know by now, Google has discontinued the Reader service, so this app is no longer functional.
Although I am very happy with the (unexpected) success of this app, I've decided to no longer update Flow Reader. This is due to several reasons: a) I built this app "for fun" and to my very specific RSS reading needs. Although I very happy to see that a lot of other people enjoyed it, I was in no way ready for attention it received (due to multiple technical and logistic reasons); b)This app was essentially just a prototype turned into a final product. The Code is very messy right now and it's becoming harder and harder to make any further changes, let alone any major ones (like background updates). c) The app is *very* tied to Google Reader backend, which means that giving proper support to another service would require a very significant amount of effort.
I am very thankful to all my users (especially the ones who donated and gave feedback!), but I hope you can understand the reasons behind this decision - continuing to work on this app would require a major rewrite and too much time trying to (once again) and make the pieces all fit with "spit and glue".
If you are interested in any future app I might develop, you can be notified about it by sending me an e-mail using the button below. You will know beforehand of any project I might be working on (and maybe even receive an alpha/beta version of it?).
Thank you again - and hopefully this won't be the end
The Developer
Click to expand...
Click to collapse
Those who have used the app please voice your support to continue the project as I have emailed the developer the link to this thread.
(Flow Reader dev here)
Right, here's what's going on:
Personally, I'm not very happy with any of the current readers on the Play Store, so the idea of building the next iteration of Flow Reader is one that I really enjoy. Unfortunately, I simply don't have the time that I would need to keep developing it any further. I now have a full time job and not much patience to keep working on the app on my spare time.
The thing is, I have several unique ideas that I believe would greatly improve the experience of Flow Reader. Actually, some of these already graduated from just ideas, as some prototyping is already done and working. I also think there is a decent amount of money that could be made from them, so I'm not very willing to just leave them out in the open.
The fact is, though, it is very unlikely that I'll ever finish this new version of the app that I'm building. I can see two options right now:
OPTION 1 - The cooperation route:
- I will pair with another developer (or a small group of developers). Bear in mind that the code is reasonably complex, so i'd rather work with someone that feels confortable around code.
- The code of Flow Reader will remain closed, but shared with the people that want to be part of this project;
- I will take care of the things that I believe to be my greatest strength: UIX and prototyping. But I will always be open to suggestions on these areas.
- The profit of the app will be split 25% (for me) and 75% (for the other developer(s)).
OPTION 2 - The free route:
- I open up the code of Flow Reader under the condition that it will forever remain open-source and free (under an attribution, no derivatives and no commercial use licence).
- I will no longer will have any direct input or cooperation on the app.
Also, I honestly think it would be better to start the app from scratch. The code is a complete mess right now so trying to build more features upon it would just be less efficient. Still, some techniques and code used in Flow Reader could be reused to save some time.
Choices
I have been a user of Flow Reader for some time and was really sad when it stopped working and that the dev stated that there was no longer going to be updates to continue after the demise of Google Reader.
That said, I totally agree that it should be continued into the post-Google Reader era of RSS news. I originally created a post on Reddit in which I stated that for the continuality of Flow one idea would be to open source the code on a git site to allow others to progress his work further.
Understandably this poses the risk of Flow Reader loosing it's (work)Flow. All that time and effort the dev put in to creating a stunning, and above all easily functional, UIX could well be lost. On the other hand the simplicity of this RSS reader coupled with its parallel article downloading feature would live on and enrich many an Android RSS fans.
So here I am on XDA, stating my opinions for the two options presented.
For the Closed Sourced Approach:
The idea of sharing the workload will mean that whoever is chosen to work on Flow Reader will most likely have a great deal of knowledge to input in to this project. It also means that the UIX will not change without considerable thought first. This I applaud.
The fact that the developer says that the proceeds of the app will be divvied up indicates to a paid app, further indicating to (hopefully) a group of developers with the incentive to push great work "out the door".
For the Open Sourced Approach:
The hands of many a developer could make this app into something even better than it already is....
...or it could ruin it with out the guidance of the one who had the vision in the beginning.
Usually in the open source community when there is a bug and/or a missing feature, if someone with the appropriate know how can fix it, it shall be done.
A question, then, to WildMoves. Would those who have donated need to pay again once it arrives back on the play store? That is if you are going to make it a paid for only app?
Either way, with the way that Flow Reader handles feeds I honestly have never, and believe never shall, discover one better. To which I would like to say that no matter which direction the dev goes, I will support and give as much feedback as I can.
Again, great work mate and keep on coding,
Skinna a.k.a Skinnx86
Skinna said:
I originally created a post on Reddit in which I stated that for the continuality of Flow one idea would be to open source the code on a git site to allow others to progress his work further.
Click to expand...
Click to collapse
Yes, when I posted my answer I was still trying to develop the next iteration of Flow Reader. I built a prototype to test several ideas before I came to the realization that I couldn't build the full app the way I wanted to in a feasible amount of time and still... well... live. :\ So I am now receptive to offset most of the workload to a developer or group of developers (hence the 25/75 profit split).
Skinna said:
A question, then, to WildMoves. Would those who have donated need to pay again once it arrives back on the play store? That is if you are going to make it a paid for only app?
Click to expand...
Click to collapse
I have the email addresses of everyone who donated, so I could probably create a mailing list to deliver full versions of the (paid) app outside the Play Store. Assuming that I would have the approval from the other developers, it would be a good sign of gratitude to those who donated, IMO.
Reasonable Thoughts
Well a man has to live. To spend your free time developing and building something you would expect some payback of some sort. But thank you for remembering us early adaptors. I know I for one will be thankful, I can but imagine others will be too.
As much as I was appreciative of the beta's being sent to us, but in case you did not hear, Facebook updated some peoples app out side of the play store. Now Google have banned out-of-market beta testing. I believe that sending an apk to install initially will work and should update through the play store correctly.
In developing countries one of the main problems aspiring web developers might face is the high cost of purchasing a laptop and getting a stable internet connection also in developed countries, lack of cell signals in the subway can pose a problem when you want to quickly edit a website(as a freelancer) as most website builders are online (wix, boomer, wordpress etc).
With OVO Web this can now be done offline and in the palm of your hands. This app attempts to edit website templates in a process I call "touch and edit" where HTML elements are clicked (on the rendered template) and their css properties/HTML contents are edited. Edited template can be published to local drive folder, ftp server or github pages .The app also comes bundled with free responsive template to get you started.
Do share your thoughts, complaints, bugs, and ways to make the app better
Download from Play store: play.google.com/store/apps/details?id=com.ovosoftware.ovoweb
Thanks MrRiko, we are a team of android developers, currently focused on improving the app(fixing bugs) and adding more features so we can't give SEO tips. If you however wanna convert your website to an android native mobile app then we can help you
True GlenCurtis, that is why we wanna make it simpler with this app, it may not be perfect but we are getting there