1
Specifically, I was exploring into a RDBMS like a MySQL for example. Reason being there's requirement for data-manipulation as well as future amendments to the data schema. Would that mean losing real-time capabilities and if real-time is overrated?
A couple of friends in programming recommended Meteor-JS for its real-time abilities but it seems like a heavy full stack MVC framework, including backend and with less support and open source stuff?
Would anyone have any opinions and views on this matter? Any experience to share app performance is very much appreciated.
What I understand is Firebase has less control but needs less codes and has less quirky errors. But that also means the data is not query-able or not as easily manipulated and search engines are not optimised to track Firebase stuff.
Would like to hear your experiences on the various backend solutions used (not exhaustive). Feel free to talk about the requirements from your project that needs various stacks.
Some other considerations I have: - scalability - costs (user number/ usage level vs. costs)- both are free until usage hits a certain level - code maintainability - code portability - device compatibility
Feature wise it would be like a simple list type of app (you could think of it as something that looks like HN) which is neutral to the platform, i.e it doesnt really matter in terms of user experience whether usage on web or mobile.
I have read that some people advocate using web application versus mobile development because its much easier to identify and solve problems and bugs, easier to write codes and build up a more scalable system. Also, mobile has more updates and crashes. Ruby on Rails for example can allow for both web/mobile especially with CSS Bootstrap.
On the other hand, some say mobile is easier because you have things like html5 which allows for cross platform codes as well as being easier to build. One can just use JavaScript, CSS and Html to bash something from say PhoneGap while on SQLite.
I have not arrived at anything conclusive and Im quite new to programming. I did look up how guys on both platforms built (such as Instagram, not because they are famous but they reveal their stack publicly :) ) but again no great insights either.
Any thoughts on the pros and cons, suggestions and questions I need to ask myself? Help is much appreciated! Thanks!!
Im wondering if its possible to build something that looks similar to Google spreadsheet on a input page (i.e I can input from a web browser) which translates to a output page as compact lines or grids?
The input and output page formats are limited (I think from CSS Boostrap), ie. they appear as single line forms which cant be inputted on a side by side basis (i.e I have to input based on text boxes for all of one column, say all countries first, then the next.) Can't we do it both vertically and horizontally together? (Reason being its easier to input and check for the accuracy of the information).
Also good to have a auto calculation such as total population etc which refreshes.
So something like for example:
Country City Population(mm) Weather Remarks +add more categories US NYC 8.4 stormy Nil US CA 38.0 sunny
Any help is much appreciated! Thanks!
I was told to validate and find pain points. However, I realized, people may be so accustomed to the current crappy solutions that they are OK to live with it. If there are free options (that works terribly), cheapos may just aggregate them. More work? Sure, but beats paying.
Perhaps its due to no other paid option that is far lower priced but offers similar value.
Conversely, instead of pain, something out of this world and offers significantly more value would get people excited and pay to try like in Dropbox or Whatsapp. Is this is a case of users having problems but don't know they exist?
How do we then go identify whats thrilling and exciting (since they are usually in a new form/ market) and go about validating and building them?
________________
"giving people something new that they can do that they find exciting and useful is a more predictable path to success than solving a pain point.
The pain point theory is deeply ingrained in the entrepreneurial mindset at this point but the problem with it is that if people have lived with some form of pain for a long time, they can probably live with it going forward, at least for quite a while. And it can be hard to get them to bite off the effort required to end the pain.
Give them something they're thrilled about, though, and at least in this day and age, they'll usually go for it.
I've heard this described as "aspirin vs vitamins" -- aspirin solves a pain point, whereas vitamins make something better. I'm talking more about a third category -- say, "Oreos" :-)"