Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
what is the difference between progressive and Responsive web app development?
check https://developers.google.com/web/progressive-web-apps?hl=en
Progressive Web Apps are many things, including responsive:
Progressive - Work for every user, regardless of browser choice because they’re built with progressive enhancement as a core tenet.
Responsive - Fit any form factor: desktop, mobile, tablet, or whatever is next.
Connectivity independent - Enhanced with service workers to work offline or on low quality networks.
App-like - Feel like an app to the user with app-style interactions and navigation because it's built on the app shell model.
Fresh - Always up-to-date thanks to the service worker update process.
Safe - Served via HTTPS to prevent snooping and ensure content hasn’t been tampered with.
Discoverable - Are identifiable as “applications” thanks to W3C manifests and service worker registration scope allowing search engines to find them.
Re-engageable - Make re-engagement easy through features like push notifications.
Installable - Allow users to “keep” apps they find most useful on their home screen without the hassle of an app store.
Linkable - Easily share via URL and not require complex installation.
https://developers.google.com/web/progressive-web-apps?hl=en#learnmore
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 10 months ago.
Improve this question
I am pretty new to web dev, and I wanted to create a simple UI in Javascript with the Google Maps Places API to familiarize myself with everything. My question is, would I just make direct URL requests with the user’s variables, or would I have to create something server side, and if so, what would I have to do?
It depends on your application's functionality. Generally, you could keep all everything on the client-side. If you app is a server-rendered one, meaning you would be using a JavaScript framework like React or Vue, you could use just the website state to keep track of users' variables and send out requests to the Google APIs to do the heavy work.
You could also look into tools like Firebase, also created by the folks at Google to handle storage or user authentication. There are rich docs on how to include Firebase in your web application for your framework of choice. This way you can create language-agnostic backend resources that conform to all of the security measures and scales automatically so you can focus on the users' experience.
In case you would like to offer some less-common functionality or have complete control over the backend you could write up an API of your own and have it deployed on a separate backend server.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I've been working on a "web app" which is actually a web site at the moment, completely vanilla, made with HTML, CSS and JavaScript; absolutely no external libraries or frameworks like JQuery, React or AngularJS.
My goal is to one day deploy the site as a webapp for mobile devices (iOS and Android), and desktops (Windows and Mac).
What is the best way to do this? What path should I follow?
Thanks in advance!
EDIT: I guess the site could be considered an app as it is SPA due to the use of JS and almost completely responsive thanks to media queries in CSS.
The main question here is: how do I get from a website app hosted on a remote server accessed via a domain, to an installable app for mobiles and desktops (.ipa, .apk, .exe, .app, etc)?
I suppose there are a few layers to this question. Let's start with some terms:
Responsive web page: A web page that works on multiple different screen resolutions (doesn't require anything more than CSS that uses media queries)
SPA: Single Page Application, this is how you get web "apps" rather than web pages. Tools like React and Angular help a lot with this, since you now need to manage things like state and routing (since you're not longer actually changing which page you are on).
PWA: Progressive Web App, this is the most modern type of web application, which tries to act very much like a native app by being capable of working without a internet connection and more.
A good way to get started down this path is to use React and their excellent tools Create React App https://reactjs.org/docs/create-a-new-react-app.html#create-react-app
This is a suite of tools that are already configured to create a SPA which is a PWA and with all the other modern tools you need to create a great web app. You'll need to read up on how to create Responsive web pages but there is plenty of resources for this, my tips are to start with media queries https://www.w3schools.com/css/css_rwd_mediaqueries.asp as well as learning Flexbox https://css-tricks.com/snippets/css/a-guide-to-flexbox/
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'm using Trigger.io to make an app I can deploy to both the app store and google play.
I'm researching baas backends that offer native sdk's for android and apple, but also offer javascript sdk's which I assume are meant for things like Trigger or Phonegap.
My question is do the app store guidelines favor one kind of back end service over another? Is javascript risky for backend? I just want to be sure before I pay for a service. The services I'm considering are cloudmine and shephertz.
They shouldn't know anything about your back-end web service.
Sounds like you are talking about making a hybird app though, which is also fine (and is technically a client). There are a ton of hybrid frameworks out there: Ionic, Cordova, Cocoon, PhoneGap, apparently Trigger.io, etc. They wouldn't be useful if app stores rejected them.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
anyone knows what are the abilities of HTML-CSS-JavaScript mobile applications (android apps) rather than animations ? what about web access and such things ?
Javascript is being very powerful language especially when we are taking about mobile applications and spa (single page applications). It can be used to load web views via ajax requests and more, it supports device APIs that allow a mobile app developer to access native device function such as the camera or accelerometer from JavaScript libraries , for example cordova . Cordova is the most known library that gives you that power.
In addition to that you can use libraries to make your application look like mobile native apps and enrich your application with functionalities (form validation , navigation, and more), examples : sencha or jquery mobile .....
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
What JavaScript Mobile development tool would you use based on momentum, existing documentation and functionality, and ability to get passed the App Stores strict policies?
Current PhoneGap release (0.8.0) released 2009-10-13 is tagged "Apple approved for App Store submissions". This blog post has more details.
I used PhoneGap to port a JavaScript game and I loved it. Unfortunately, the game was too slow (Mobile Safari is slow when you make changes to the DOM, and I was moving divs around as sprites) and I switched to native.
But since some people started getting having their PhoneGap apps rejected, I have become shy of the project. I'd love to hear an official stance from Apple, but I don't know if it'll ever come.
I found Phonegap to be the easiest to use. However Quickconnect seems to be more ambitious in terms of multi-platform support, the author tells me that Quickconnect has been used in many apps (but couldn't disclose which). Supposedly Phonegap apps were being rejected because those submitting were loading the entire apps off the web, however the framework does seem sluggish. Apple has not replied to the Phonegap team about the app rejection.
If I had to make a choice it would be Phonegap at this stage, but unless you really want the app on multiple platforms I don't see why you wouldn't use the great tools provided by Apple for native development.
At this point you might also want to look at Titanium by Appcelerator.
The development process is pretty simple, and they support both the iPhone and Android platforms.